Setting Admin Permissions in your project
Inviting and managing your admins and their permission rights to your Regpack project(s) is easy.
First, you need to decide which admin should have access to which project(s) and if you are going to be any limitations (permissions) on what they can view and edit within a certain project.
Note: Access to Admin Management is limited to the owners of an organization. There can be more than one owner for an organization, but all are billed at the Super Admin level.
Begin by navigating to “Settings” then click “Admin Management“.
In the Admin Management section, you can invite new admins, upgrade/downgrade existing admins, edit admin billing levels, edit admin permissions per project, grant/revoke access to specific projects, and edit admin passwords.
To edit a specific admin, first, click their name. A side panel with their admin details will populate Profile, Projects, and License & Billing.
- Profile: Edit an admin’s login email, name, owner status, and password.
- Projects: Grant/revoke access to specific projects and edit admin permission levels per project.
- Billing: Upgrade or downgrade an admin level (Super Admin, Financial, API, Collaborator, or Guest).
When finished, click “Update Profile”, “Add Project”, or “Update Admin Level” respectively so the new information will save and take effect!
Per Project Permissions
It’s possible to control the access each admin has to information on a per-project level.
For any admin, under the “Projects” tab, you can:
- Enable or disable access to all projects.
- Set specific access permissions per project.
Click “Add Projects” at the bottom to add specific projects: either if the “grant all projects” is disabled OR to set up specific permissions for specific projects if “grant access to all projects” is set to enable.
Example 1: Edgar C. is an admin and has access to all projects. There are no projects listed below, which means that Edgar C. can access all projects in the organizations with 0 restrictions. This includes any new projects created.
Example 2: Maya Z. is an admin and does NOT have access to all projects. You’ll notice that the setting “Grant access to all projects of the organization” is disabled. However, by clicking the “Add Project” button, she is given access to 1 project only. It is marked as “Full Access” but you can edit this and set further permissions per project.
Example 3: Below shows another admin with enabled access to all projects (which means they will be given access to all future projects created as well), but with specific projects listed underneath as well. This allows you to restrict access to specific projects, but give the admin access to all other projects in your account.
By hovering over individual projects, you can click “Set Permissions” to set up project-specific permissions.
The default is just access based on their administrator license billing type.
Click “limited access” and you are given options like:
- Which users the admin can view
- Module-level access includes limiting access to project settings, products, reports, emails, and forms.
