Respresso has the following project roles ordered by priority:
There are no restriction over these roles, except that each project must have an admin.
This is why an admin must transfer his role to another user before he can leave the project.
(Except if he is the last user in the project, then the project will also be removed.)
Project management actions by project roles
|Manage project settings (name, token, etc.)||Yes||No||No||No|
|Manage project invites, join requests, members and their roles||Yes||No||No||No|
|Create token for integrations (Figma, Adobe XD and Zeplin)||Yes||Yes||No||No|
|List all users in project||Yes||Yes||Yes||Yes|
Resource management actions by project roles
|Change Flow configurations||Yes||No||No||No|
|Manage versions (new, copy, finalize, patch, merge)||Yes||Yes||No||No|
|Create or delete resources (including import and upload)||Yes||Yes||No||No|
|Edit sensitive resource details (e.g.: key, image dimensions)||Yes||Yes||No||No|
|Edit resource content (e.g.: localization value, image)||Yes||Yes||Yes||No|
|View all resources and download generated files||Yes||Yes||Yes||Yes|
All the users with project member role can edit all the resources you manage in Respresso. Although, they are restricted to be able to change only resource contents. When you use the default Flow configurations, members should not be able to break anything in the application.1
As a rule of thumb, you should keep users’ access roles as low as possible. This can prevent errors and unauthorized or unintended modifications.
There is a list of our recommendations for the most common project members:
EditorIn case of Flow customizations:
Editor(Designer tool integrations require resource additions)
ViewerIn case you want to allow them to fix typos:
ViewerIn case you want to transfer some responsibility:
- Managers and POs:
Someone must have the
You can assign the team lead or the project manager for this as they should manage the project members and their roles.
- If you rely on additional syntax/semantic within your resources' content than a project member can also cause problems.↩