Skip to content

Company permissions overhaul #74

Description

@orthecreedence

Right now, permissions are rigid. Members have permissions, and those permissions apply to all objects within the company.

There needs to be a more granular approach. Instead of a member-company permission, it would be a member-company-object permission, where object can be all objects or a specific object.

At some point (or even in this iteration) we might want to add "groups of objects" (like, tagging) such that permissions are member-company-tag/object.

Activity

added
tag:propertyHaving to do with use/stewardship with property or resources
tag:securityRegarding the security or privacy of various Basis systems
type:discussionDiscussion or ideas for future direction, input welcome (don't be shy)
on Aug 3, 2020
added this to the Roadmap milestone on Aug 3, 2020

orthecreedence commented on Aug 3, 2020

@orthecreedence
MemberAuthor

I'm adding the property tag because this will likely pave the way for how resources are managed within a group (productive or not).

added
layer:coreRegarding the core protocol (cost tracking, transactional fabric, etc)
on Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    layer:coreRegarding the core protocol (cost tracking, transactional fabric, etc)project:coretag:propertyHaving to do with use/stewardship with property or resourcestag:securityRegarding the security or privacy of various Basis systemstype:discussionDiscussion or ideas for future direction, input welcome (don't be shy)

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions