What are the different roles assigned to an inca account?

Modified on Sun, 9 Mar at 11:57 PM

Role Descriptions 


1. Admin 

  • Overview: Admins are the highest-level users with comprehensive access and control over the entire inca platform. They have full capabilities to manage clients, platform credits, and client projects. 


  • Responsibilities: 
    • User Management: Can invite new users, assign roles, and edit permissions for existing users. 
    • **Platform Credits: Full access to view, purchase platform credits. **Coming soon
    • Client Access: Unrestricted access to all clients, with the ability to create, edit, and manage projects, dashboards, and AI coding instances as well as add new clients. 
    • Permissions: Editor level access to all projects, and AI coding instances across all clients.



2. Account Manager

  • Overview: Account Managers have extensive access similar to Admins but are primarily focused on managing client accounts and projects. They cannot manage platform credits. 


  • Responsibilities: 
    • User Management: Can invite new users and edit permissions of existing users within their assigned scope. 
    • Platform Credits: Can view platform credits. Cannot purchase new credits.
    • Client Access: Unrestricted access to all clients, with the ability to create, edit, and manage projects, dashboards, and AI coding instances. 
    • Permissions: Editor level access to all projects, and AI coding instances across all clients.



3. Project Manager

  • Overview: Project Managers have targeted access focused on managing specific client projects and AI coding instances

  • Responsibilities: 
    • User Management: No permissions to invite or edit other users. 
    • Platform Credits: Cannot view platform credits. Cannot purchase new credits. 
    • Client Access: Restricted to client-specific permissions, allowing them to manage projects and AI coding instances only for assigned clients. Cannot create a new client (in either Project Builder or a new AI coding instance) 
    • Permissions:
      • Editor: Can create, edit, and fully manage projects and AI coding instances.
      • Collaborator: Can collaborate on projects and AI coding instances with some editing capabilities. 
      • Viewer: Can only view projects and AI coding instances.


4. Guest

  • Overview: Guests have the most limited access, suitable for external collaborators who need to view or contribute to specific projects without full management capabilities.

  • Responsibilities: 
    • User Management: No permissions to invite or edit other users. 
    • Platform Credits: No access to platform credits. 
    • Client Access: Restricted to client-specific permissions, allowing access only to assigned projects and AI coding instances. Guests can only have Collaborator and Viewer permissions to clients. (in either Project Builder or a new AI Coding instance). They cannot be assigned Editor permission to any client. 
    • Permissions: 
      • Collaborator: Can collaborate on projects and AI coding instances with some editing capabilities. 
      • Viewer: Can only view projects and AI coding instances. 



Summary of Permission Matrix




Note: Archiving or deleting platform projects (survey) and deleting inca AI coding projects are only applicable to Admin users only.



How client-specific permissions work 


Client-specific permissions allow access (as per the specified level - Editor, Collaborator or Viewer) to specified clients, which means that users are able to access all projects associated with that client. 


Click the drop-down button to select the specific client(s) then select the permission level for each client



Suppose User A is a Project Manager who has been given: 

  • Collaborator access to Client X: User A can collaborate and make some edits to projects related to Client X (i.e. Nexxt). 
  • Editor access to Client Y: User A can create, edit, and fully manage projects and AI coding instances for Client Y (i.e TEMPLATE).



User A will not have any access to projects related to clients other than X and Y unless additional permissions are granted OR they’ve given an “all clients” permission. 


Note on the "All Clients" permission :


There is an option to assign "All Clients" permission, which grants the specified level of access (Editor, Collaborator, Viewer) across all clients. 





Adding clients to projects  


Clients can be added during project creation or when editing the project in the builder


Adding clients to AI Coding instances


Clients can be added to AI Coding instances when they’re created. Clients can also be added to or updated when AI Coding instances are edited. 


 



It’s important to note that users with only Editor access to clients can create new projects. What that means, is that users that do not have Editor access to any client, do not have the option to create a new project. Similarly, when creating a new project, users can only assign the project to a client to which they have editor access. Since Admins and Account Managers have Editor access to all the clients by default, they don’t face this restriction.

Let’s understand with an example. User A is a project manager who has been given Collaborator access to all clients. This user is not allowed to create new projects. 




Now let’s modify the permissions a little for User A. Let’s add Editor permission for the client “HotWheels”. They can now only assign a new project to the Hotwheels client.



If they try to add a new client, they get this error message 





To learn more about inviting a new user, please see this article HERE.  

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article