Some certifications belong to organizations, such as companies or training providers, rather than to individuals. People at that organization sign in to the Portal as contacts, and each contact has a contact role, such as primary contact or HR manager. Contact-role permissions decide which roles can act for the organization in Certifications.
What It Controls
The Contact-Role Permissions page shows one row for each active contact role in your Rhythm account. It also includes one row for all contacts, regardless of role. Each row has four permissions:
- Apply for certification — the role can start certification and transfer applications for the organization.
- Renew certification — the role can start renewal and reinstatement applications for the organization.
- View applications — the role can see the organization's applications on the Portal's My Applications page.
- Training provider administrator — the role can act as an administrator for the training provider organization.
These permissions apply only to Portal actions taken for an organization. They decide whether a contact can see and start application or renewal processes for their organization, instead of only for themselves. They also decide whether a contact can see applications submitted by other people at the organization.
A contact at a parent organization can apply on behalf of a descendant organization and see that descendant's applications when they also have the appropriate parent/child organization-management roles and permissions.
If a contact's role is marked as administrative in your Rhythm account's contact-role setup, that contact can apply, renew, and view applications for their organization regardless of this grid. This page does not show that exception.
Where to Find It
Go to Certifications › Setup › Contact Roles. The Contact Role Permissions Settings page opens with the all-contacts row at the top, followed by one row for each active contact role.
Prerequisites
- You need the permission your administrator grants for Certifications settings.
- You must save the base Certifications Settings record before this page shows its grid.
- The contact roles you want to grant permissions to must already exist and be active in contact roles setup. Inactive roles do not appear as rows.
The Settings
| Setting | Options | Default | Effect |
|---|---|---|---|
| All-contacts row | Four permissions | Unset | Grants a permission to every contact at every organization, regardless of role. It does not grant training-provider administration to anyone, because that permission matches by role. |
| Per-role permissions | Four permissions per active contact role | Unset | Grants the permission to a contact who holds that role at their organization. |
Dependencies and Precedence
- These permissions live on the same settings record as Certifications Settings. Until you save that page once, this page shows a message asking you to save it first and does not show the grid.
- Deleting a contact role or a program does not remove it from this grid if it is still named here. The outdated name simply matches nothing until you clean it up.
- A contact's organization role controls what they can do in the Portal for their organization. Their staff permissions do not affect these Portal actions, and these permissions are separate from any Certifications staff permission in the Console.
Change Impact and How to Revert
- Granting a permission to the all-contacts row affects every organization in your Rhythm account at once, not just the organization you had in mind.
- Removing a tick from a role removes that permission the next time you save the grid. It does not change anything the contact already did.
- This page does not show who changed a permission or when. Changes to the full settings record appear in your Rhythm account's audit history.
Permissions
You need the permission your administrator grants for Certifications settings to view or change this grid. The grid does not have a separate permission.
Validation and Errors
Warning
The Portal's My Applications page should show only the applications a contact submitted themselves, unless their role permissions allow broader visibility. If a contact without the View Applications permission for their role sees applications submitted by other contacts at their organization or a descendant organization, that is not intended. Check the contact's role and this grid, and report it to Support if the role has no View Applications permission ticked.
- If the base Certifications settings have never been saved, the page shows a message instead of the grid and blocks all changes until you save that page.
- If your Rhythm account's contact roles fail to load, the page shows an error and stays on its loading state. Reload the page to try again.
Related
See "Related" in the sidebar for the Certifications settings record, setting up contact roles, and managing a contact's organization and role history.