Core concepts
User roles
Every team member can have a user role to restrict and clearly define the functionalities that user can perform in the team.
User role allows for granular control over data access, feature usage, and overall application functionality!
It helps ensure that team members have appropriate access rights based on their responsibilities and contributions, while also maintaining security and compliance within the application.
What is a user role?
A user role refers to the specific permissions, access rights, and responsibilities assigned to each member within the team. User roles are used to define and manage the level of access and functionality that each team member has within the application.
What are the different user roles available?
There are several user roles. One fixed and three assignable roles to be precise.
⚡ Owner
Owner is not an assignable role!
The person who creates a team will be the owner. This role cannot be transferred nor changed. This is fixed!
This is the only role that cannot be assigned, but set by default when a person creates a team.
Some features / permissions exclusive to the owner
are the following:
- Only an
owner
can delete a team. - Only an
owner
can add or assign a domain to a team.
⚡ Administrator
An Administrator
is the next highest role after owner
. Administrator
can perform the following actions.
- Can rename a team.
- Can invite new members to a team.
- Can change member roles.
- Can remove a member from a team.
- Can set default domain.
- can change the default privacy & security settings of a team.
Available permissions
API Token permissions for 'Administrator' user!
When creating an API Token
, the user with Administrator
privilege can select any combination of the below permissions
link:read, link:create, link:update, link:delete, link:click:read,
link:click:reset, link:metrics:read, member:read, member:create,
member:update, member:remove, team:read, team:update, team:metrics:read
⚡ Member
An Member
is the next highest role after Administrator
. Member
can perform almost all actions related to a link.
Available permissions
API Token permissions for 'Member' user!
When creating an API Token
, the user with Member
privilege can select any combination of the below permissions
link:read, link:create, link:update, link:delete, link:click:read,
link:click:reset, link:metrics:read, member:read, team:read,
team:metrics:read
⚡ Read only
This is the least privileged user role of all roles. As the name suggests, it is literally 'view' anything, but not create, delete or update anything in a team!
- A
read-only
member will not be allowed to create/edit/delete links.
Available permissions
API Token permissions for 'Read-only' user!
When creating an API Token
, the user with read-only
privilege can select any combination of the below permissions
link:read, link:click:read, link:metrics:read, member:read,
team:read, team:metrics:read