Design the company structure

Before you start

The structure connects employee records to managers, calendars, reports, and permissions. Start in Settings and create levels from the top down: legal entity, office, then team. Add shared resources afterwards, once you know which office owns them.

You need permission to manage settings. You can only maintain offices and teams within your management scope.

Create a legal entity

Open Legal entities and select Add. Only the name is required at creation. Talento initially copies the account's general values and creates a default office for that entity.

Edit the entity afterwards to complete:

• legal name and tax identifier;
• manager;
• country and region;
• time zone, currency, and language;
• contact email address.

Use a separate legal entity when a company or division must issue documents under its own details. Do not duplicate an entity simply to represent a site; use offices for that.

✓Tip

Review tax and regional details before configuring invoicing, calendars, or new offices. Those workflows depend on the structure defined here.

Create an office

Open Offices and select Add. Enter a recognisable name, its legal entity, and, where relevant, its parent office. Complete the manager, country, region, currency, annual leave days, time zone, and language.

Enable geolocation when time tracking needs to verify location. Mandatory geolocation applies stricter controls, so communicate and test it before rolling it out to the team.

Each office also maintains its own invoice series. If the office will issue documents, review Invoicing settings before starting.

iInformation

For offices in Spain, Talento can prepare public holidays for the selected country and region. Always review the resulting calendar and add any missing local holidays.

Organise offices and teams into hierarchies

Use a parent office to represent dependent sites. When one office is assigned beneath another, both remain under the same legal entity.

In Teams, create each team with a manager and, where applicable, a parent team. The hierarchy represents areas and subteams without repeating names or using teams as informal labels.

Before saving, confirm three points:

1. the assigned manager reflects the real responsibility;
2. the parent level is correct;
3. you are not creating a cycle or a duplicate with a slight variation of the same name.

Office and team managers can also be used in approval rules. See Approval rules before basing a workflow on them.

Outcome

You can verify the result on the configuration page, in the list, or in the state described in the steps above.

Common problems

If an option does not appear, check the active module, the specific permission, and the record's scope. If the configuration is correct and the problem continues, save the displayed message and contact support.