Skip to content
Documentation
Explore guides

For administrators

Create and configure a group

Define which features the group can use and which employees it can act on. This article is for people who configure or administer this feature.

Contents

Before you start

Talento uses permission groups to decide who can enter a feature, which actions they can perform, and which employees they can manage. A group might represent team managers, HR, Finance, or Recruitment.

Configuration has three steps:

  1. What the group can do: a permission level for each feature.
  2. Who it can act on: the employee scope that the group can view or manage.
  3. Who receives access: employees, teams, offices, companies, or roles assigned to the group, including the dates when access applies.

Information

A manager role and a permission group are related but different. The role describes a person's general position; the group defines the access Talento actually applies.

Create a permission group

  1. Open Permission groups.
  2. Select Add group.
  3. Enter a name that describes the intended audience or responsibility.
  4. Add a description and, if it helps you recognise the group, a colour.
  5. Save, then review every permission before assigning the group.

Avoid ambiguous names such as “New group” or “Special access.” Names such as Store managers or Recruitment team make later reviews clearer.

Choose what the group can do

In the first step, Talento organises permissions by area. For each feature:

  1. Decide whether the group needs it.
  2. Choose Read, Create, or Manage only when necessary.
  3. Review personal data, salaries, invoicing, and configuration especially carefully.
  4. Check the changes before continuing.

Changes are saved from the same screen. Review areas you do not use as well: creating a group does not replace a complete permission check.

Define who the group can act on

The second step defines management scope. Depending on the available options, you can use criteria such as company, office, team, or role.

Scope is especially important when the group has Manage permission. A team manager may need to act only on direct reports or their team, while HR may need a broader scope.

If the group only has Read or own-content Create permissions, scope may have less effect, but it should still be configured consistently for future reviews.

Warning

Broad permissions combined with excessive scope can expose information or actions that the employee does not need. Validate the complete combination, not each step in isolation.

Result

You can verify the result on the settings page, in the relevant list, or through the status described in the steps above.

Common issues

If an option is unavailable, check the active module, the specific permission, and the record scope. If the settings are correct and the issue continues, keep the displayed message and contact support.