Inviting and managing your admins and what they have access to in your Regpack project (or projects) is easy.
First you need to decide which admin should have access to which project(s) and if you are going to place any further limitations (permissions) on them in a certain project.
Remember, 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.
Start off by going to “Settings” and clicking “Admin Management“.
This will place you in the Admin Management section, which is where you can invite new admins, upgrade/downgrade existing admins, edit admin billing levels, edit admin permissions per project, grant/revoke admin 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: this is where you can edit their login email, first name, last name, owner status, and password.
- Projects: this is where you can grant/revoke access to specific projects and edit their permission levels per project.
- Billing: this is where you can upgrade or downgrade their admin level (super, assistant or view only OR super administrator, collaborator, or guest).
When done, remember to click “Update Profile”, “Add Project”, or “Update Admin Level” respectively so the new information will 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 setup specific permissions for specific projects, if “grant access to all projects” is set to enable.
In the example below, admin “Edgar C” 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.
In the example below, admin Maya does NOT have access to all projects. You will 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 click this and set further permissions per project.
Lastly, the example below shows an 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 including limiting access to project settings, products, reports, emails, and forms.