Within this article:
Once the account of a user is created and linked to your company, it is time to think to complete the task by attributing them a role and at least an entity.
The attribution of roles may be done at the Company level or at the Entity level, with the idea of refining the handling and managing of access levels, in addition to using several features available within the LittleBig Connection platform.
We will see henceforth what are the roles and access levels that you and your collaborators may have. .
Company Level
In order for a new user to have access to the settings and reporting functions, it will be necessary to assign them a role at the Company level. These two roles are: Company Administrators and Buyers.
 |
 |
 |
||
| Company Administrator | Buyer | Standard users | ||
|
They are responsible of setting up the company and managing the configuration and users of the account globally. This role enables you to see and handle all the objects within the company and to use the reporting feature (Data stories) at the highest level. You will have the option of extracting all data of the account in Excel or CSV format. |
|
They are responsible for the management of budgets and spending lines created within the account. Buyers also have access to Reporting functions concerning budgets and spending lines, they may also extract global data from the account. In some instances, buyers may be set up as validators at the last point of the validation process to select a supplier. |
|
This is the default role a user may have once their account has been created. This type of user is not able to access most of the functions available and their access to data is very limited. It is necessary to give them a role in order to enable them to have the required degree of visibility. |
.
Company Administrators:
Company administrators enable you as a user to have the highest level of control over the settings of the account and the assignation of roles of other colleagues, as well as complete visibility on all reporting criteria that needs to be accessed.
Permissions would include:
- Create and manage company account settings including the creation of Entities
- Add collaborators
- and assigning them a role at the level of the Company (including buyer role permissions)
- and assigning them a role at the level of the Entity (Entity manager, Operational manager or Operational)
- Handling of received assignation requests to the Company account and to the entities within
- validation of any requests to join the company from collaborators not yet registered
- removal of access to collaborators that are no longer part of the company
- modification of the assignation and roles of other collaborators within each and every entity
- Viewing of all objects within the company account including Requests for Proposal, proposals, missions, timesheets and invoices
- Full access to the reporting module for the account (Data Stories)
- Possibility of exporting all data within the account in Excel or CSV format
.
Buyers:
The role of Buyer is responsible for managing budgets and spending lines, created within the Company account. Based on the settings of your account, the role of Buyer may be tasked with either validating the selection of a new supplier, prior to starting a mission and/or validating the Purchase Order.
Permissions would include:
- Handling of budgets and spending lines
- determining the currencies used within the account
- determining and supervising reports concerning budgets and spending lines
- Setting up validation limits/thresholds at the time of creating Purchase Orders, where they may also be assigned as validators once certain amounts are reached
- Access to the reporting module within the account (Data Stories) is to come
- Possibility of exporting all data within the account in Excel or CSV format
When the premium feature "Negotiation Module" is activated in the account, it would be possible for Buyers, to negotiate the price and conditions of the service, with the supplier.
.
Entity Level
In order for a user to be able to create new Requests for Proposal, and follow up on missions created in the platform, they have to be positioned or assigned to at least one entity. Once they have been assigned to an entity, it will be necessary to assign them a role.
Three roles are available, first we have the Entity Administrator, second we have the Manager (default role) and finally the Operational role.
 |
 |
 |
||
| Entity Administrator |
|
Manager |
Operational role | |
|
Entity administrators (entity lead and deputy manager) may see and edit RFPs, proposals, POs and Timesheets, for the collective of entities and sub-entities they are assigned to. In certain cases, if the entity includes a workflow within, the Entity administrators will also be able to have a validation role within the publishing of new Requests for Proposal. |
|
Managers may see and edit RFPs, proposals, POs and Timesheets within the entity they have been assigned to only, however they will not have visibility on the sub-entities it may contain.
This is the default role given to a user that has just been assigned an entity upon its creation. |
|
The role of Operational users means they are able to create and edit new RFPs, proposals, POs and timesheets within the scope of the entity they have been assigned to only. They will however not be able to view any content corresponding to any related sub-entities. Unlike Entity Administrators and Managers though, they will not have any visibility on any content they have not been directly assigned to. |
.
Entity Administrator (Entity Lead and Deputy Manager)
In this role, you would be the equivalent of the company administrator at the entity level. You will be responsible for all entities and sub-entities, as well as all objects encompassed within them, such as RFPs, POs and Timesheets. This means that you would have full visibility on all the elements within the scope of the Entity.
You would be able to:
- Create new Requests for Proposals
- Qualify/rate received proposals
- Create Purchase Orders (if a validating Buyer has not been configured)
- Stop or renew Purchase Orders
- Validate Timesheets
- Be assigned as the person responsible to validate new Requests for proposals when a workflow is in play
For the position of Entity Administrator, it is required to have a dedicated Entity Lead and Deputy Manager assigned as a back-up, in case the Entity Lead is not available.
Whenever Workflows are configured within an entity, note that only the Entity Lead will be notified * to check and validate the publication of the new Requests for Proposal, although the Deputy Manager will also be able to carry out the validation.
* In case the Entity Lead is not available, and to allow the Deputy manager to receive the notifications for the workflow validation in their stead, it will be necessary for the Entity Lead to change their availability to "Away". This may be done by accessing the bottom part of the menu on the left part of the screen and clicking on the option " Available" and selecting the option "Absent" from the dropdown.
 |
.
Manager
This is the default role that all new users that have just been assigned to an entity will have.
Within this role, you would be responsible for:
- The creation of new Requests for Proposals
- Qualifying/rating of received proposals
- The creation of new Purchase Orders (if a validating Buyer has not been configured)
- Stopping or renewing Purchase Orders
- Validation of Timesheet
The Manager will have visibility on all the elements included within the entity, however they will have no visibility on any and all sub-entities that depend on the one they have been assigned to.
.
Operational Role
This level of access has been created with the purpose of managing different levels of confidentiality.
In this role, you are able to carry out the following actions within the scope of the assigned entity:
- Create new Requests for Proposals
- Qualify/rate received proposals
- Create Purchase Orders (if a validating Buyer has not been configured)
- Stop or renew Purchase Orders
- Validate Timesheets
Unlike Entity Administrators and Managers though, you would only have visibility on the RFPs, POs and Timesheets that you have been assigned to directly.
This means that a person with the Operational role may not select any other operational manager, other other than themselves, when they create a new Request for Proposal within the scope of the Entity they are limited to.
 |
Note that this role is not cumulative with any other role within the platform. This means that someone with the role "Operational" within an entity cannot be assigned the role of Manager or Entity Administrator within any other entity, nor can they be assigned a Company Role. |
.
Summary of Roles and Responsibilities of collaborators
* In the instance the optional validation steps have been set up, note that these factors may be modified by the Company administrator only
Please click below to download this table in English