About company roles
Every user on a company team has a role.
For paying companies, a person's role determines their billing status – whether or not they are counted as a billable user.
A user’s role also controls what permissions they can have for other parts of DeepStream, such as Requests and the company Profile.
There are two company roles: “Full user” and “Authorised stakeholder”.
Full user
This role is intended for a primary user of the platform who will be creating, administering, or overseeing procurement activity directly.
Users with this role can be provided access to all aspects of the system depending on the configuration of their individual permissions.
Users with this role are typically counted as billable users.
Authorised stakeholder
This role is intended for a secondary, indirect user of the platform who will be tasked with managing or responding to specific, defined aspects of individual requests.
Users with this role can be given a fixed set of capabilities designed to provide limited access to request-based functionality only.
Users with this role are typically counted as non-billable users.
Comparison
Scope |
Capability |
Authorised stakeholder |
Full user |
Company |
“Manage users” permission |
❌ |
✅ |
“Edit profile” permission |
❌ |
✅ |
|
“Create requests” permission |
❌ |
✅ |
|
“Receive requests” permission |
❌ |
✅ |
|
Request |
“Owner” role |
❌ |
✅ |
“Team member” role |
✅ |
✅ |
|
“No access” page permission |
✅ |
✅ |
|
“Can read” page permission |
✅ |
✅ |
|
“Can comment” page permission |
✅ |
✅ |
|
“Can respond” page permission |
✅ |
✅ |
|
“Can edit” page permission |
❌ |
✅ |
✅ denotes where a capability is available for a given role but it is still possible to switch this capability off for individual users as required.
Requests
Users also have a separate role and permissions for individual requests they are added to.
For more information see this article on Request roles.