Skip to main content

Common access setups in Grow

Find the right combination of admin permissions, app role, and Grow role for the most common access requests in Grow.

Most access requests in Grow need a combination of settings, not just one. Each setup below shows what to set in each layer, where to find the steps, and what the person still won’t have. If you’re new to the layers, start with How access works in Grow. For how admin permissions and app roles work across Tellent, see How access works in Tellent.

Note: The three layers in each table are admin permissions, app role, and Grow role. Managers get their access from the reporting line, so see setup 5.


1. Everything, including performance data

Use this for someone who needs to manage settings, accounts, and performance data.

Layer

Setting

Admin permissions

Full access

App role

Administrator

Grow role

HR

Steps: Set admin permissions and the app role as described in Manage team members. Then set the Grow role as described in the HR and Group HR section of Who can do what in Grow.

What they still won’t have: Nothing role-based in Grow is left out. Being a manager of specific people comes from the reporting line, not from these settings.


2. Company settings and user management, without performance data

Use this for someone who handles setup and accounts but shouldn’t read reviews, goals, or survey results, for example an IT or technical administrator.

Layer

Setting

Admin permissions

Administrative access or Full access

App role

Administrator

Grow role

None

Full or Administrative? Full access manages all organization settings. Administrative access covers only the areas you select, for example managing users or managing billing. Choose Administrative access if the person shouldn’t manage everything. Grow settings come from the Administrator app role, not from admin permissions.

Steps: See Manage team members for the admin permissions and app role. See the Administrator section of Who can do what in Grow for what Administrator includes.

What they still won’t have: Performance data. They can’t read reviews and talent reviews, and they have no access to goals, training, skills, or survey setup and results. They can’t see these even though they have Administrator access. If they need them, add the HR role.


3. Performance data for the whole company, without settings

Use this for someone who runs reviews, campaigns, and surveys for everyone but shouldn’t change company settings.

Layer

Setting

Admin permissions

No permissions

App role

Employee

Grow role

HR

Optional: Add Administrative access if the person should also handle team member accounts. The HR role alone can’t create or deactivate accounts.

Steps: Set the Grow role as described in the HR and Group HR section of Who can do what in Grow. For the optional step, see Manage team members.

What they still won’t have: Grow company and feature settings and integrations (these come from the Administrator app role). Without Administrative access, they also can’t manage team member accounts.


4. Performance data for some groups

Use this for someone, such as a department head, who should see and manage performance data for one or more groups only.

Layer

Setting

Admin permissions

No permissions

App role

Employee

Grow role

Group HR

Create the groups first. Go to Settings > Grow groups to create and fill them. Then give the person the Group HR role for those groups. The person doesn’t need to be a member of the groups.

Steps: See the HR and Group HR section of Who can do what in Grow.

What they still won’t have: Group HR is HR limited to selected groups, with these limits:

  • They can’t create new flexible campaigns or campaign templates.

  • They have no access to pulse, journey, or custom surveys.

  • For legacy engagement surveys, they see results only for surveys they created.

  • In talent reviews, they can’t open the campaign overview unless they created the campaign.

  • Skills aren’t limited to groups. They apply company-wide.

  • They have no Grow company or feature settings, and no account management.


5. Managers

Use this for people who lead a team and need to see their reports’ information.

Layer

Setting

Admin permissions

No permissions

App role

Employee

Grow role

None. The reporting line is the only configuration.

Steps: Make sure each employee has a manager assigned. Then choose in Settings > HR (Grow), under What managers can see, whether managers see direct reports only or their full reporting line. See the managers section of Who can do what in Grow.

What they still won’t have: Managers can’t create or manage review campaigns or surveys. They see flexible campaign content for their reports only if they’re involved in the review.


Examples

  • A People team that runs reviews and manages accounts: setup 3 with the optional Administrative access.

  • A department head who runs reviews for their department: setup 4.

  • A technical administrator who handles SSO and accounts: setup 2.


Did this answer your question?