Access Levels
Organisation Owners set each member of an Organisation up as an Owner, Member, Agent. Access levels control what viewing and editing permissions each participant has on Salt.
Owner level
An Owner has control over the entire organisation and accounts they’ve set up.
Owners can:
- Edit collaborators (including access levels and statuses)
- Edit Organisation name
- Edit Policies
- Access information about the Robo Guardians
Whoever sets up an Organisation is automatically the Owner, and can add additional Owners or Members.
Owners can see and manage all of the organisation’s members in the Settings menu.
Member level
A Member has visibility across many areas of the organisation. They cannot create accounts or add new users.
Members can:
- View all accounts
- Sign transactions on Accounts they are signers on, as set up by the Owner. Transactions must adhere to policy rules.
- View all transactions
- View all collaborators in the Organisation
Agent level
An Agent is an external entity that can be added as a co-signer when creating an Account. Restricting what an Agent can do on the Account is set by Owners, using Policies.
For all Accounts that are created with an Agent as co-signer, the Agent is initially automatically disabled.
Using the SDK, an Owner can enable the Agent as a co-signer using the PolicyType denied_proposers.
Agents can:
- Sign transactions on a specific Account, set up by the Owner.
- Only view the account they've been added to.
- View the policies pertaining to that account.
Overview: Access Levels
| Permission | Owner | Member | Agent |
|---|---|---|---|
| View own profile (name, role, etc.) | ✅ | ✅ | ✅ |
| View accounts | ✅ | ✅ | ✅ (own account only) |
| View policies | ✅ | ✅ | ✅ (own account only) |
| View organisation collaborators (access levels, status) | ✅ | ✅ | ❌ |
| View all organisation accounts | ✅ | ✅ | ❌ |
| View organisation portfolio dashboard | ✅ | ✅ | ❌ |
| Edit organisation name | ✅ | ❌ | ❌ |
| Edit organisation collaborators (access levels, status) | ✅ | ❌ | ❌ |
| Add new collaborators (via EOA) & assign name/role | ✅ | ❌ | ❌ |
| Edit collaborator information (name, role) | ✅ | ❌ | ❌ |
| Change collaborator status | ✅ | ❌ | ❌ |
| Edit accounts | ✅ | ❌ | ❌ |
| Edit policies | ✅ | ❌ | ❌ |
| Access Robo Guardians | ✅ | ❌ | ❌ |
Adding and removing users
Owners
An organisation must always have at least one Owner, and ideally will have two or more. Multiple owners lessens the risk of losing full organisation access.
Only Owners can add and remove other Owners, or ‘promote’ Team Members to the Owner level.
If there is only one Owner, ownership can be ‘transferred’ by adding a new Owner, and then removing oneself as Owner.
Members
Organisations do not need to have any team members.
Only Owners can add Members. Members can reject invitations, and/or remove themselves from an organisation.
Access rights
Access rights are tied to a user’s cryptographic identity. Users are authenticated by connecting with their browser wallet. Each wallet address (EOA) is treated as an individual user, regardless of who actually ‘owns’ each address.
The access levels within Salt are tied to that wallet address (EOA).
When someone creates an Organisation, they are automatically assigned as an Owner. Then, the Owner will need to invite at least one more person to join the organisation. Those subsequent members can be assigned any role, including Owner.
Having 2-3 Owners in your Organisation allows for redundancy.