Getting started as a deputy

You are in the right place if

Your access was created from the Deputy profile, one of the predefined profiles available to access the back office.

On an account split into departments, the administrator profile is not offered: the deputy is the most complete predefined profile available.

In short, the deputy holds the same rights as the administrator, minus the account configuration.

You handle day-to-day: content, distribution, engagement, statistics, and you grant access. What each of those families of rights covers is explained in Understanding custom permissions.

What the profile covers

• All content: create, edit and publish, including capsules written by other people. None of your capsules require validation. You also manage categories and skills, which the content creator profiles do not.
• All distribution: access every group and every track, manage them, create new ones, notify everyone.
• All engagement: forum, notifications, campaigns, sessions and registration approval, badges and certificates.
• All statistics, including AI Agents statistics when your account has them.
• Departments and authorizations: you shape the account structure with the Edit / add departments right, and you assign profiles with the Edit / add authorizations right.

What you lack compared to the administrator

The difference is entirely in account configuration. You can’t:

• Change the platform customization;
• Edit or add the IT integrations;
• Have full access to user data;
• Create custom authorization templates: you assign the existing profiles, but you do not define new templates;
• Manage AI Agents of the Animation menu: on accounts that have AI Agents, running them remains the administrator’s job. AI Agents statistics do remain available to you;
• Connect as a learner: seeing the platform through a specific user’s eyes isn’t part of this profile. That action also depends on an account option, so even an administrator won’t see it if that option isn’t enabled.

These screens and those buttons simply won’t appear for you. Before concluding that something is broken, read Why can’t I see this feature?.

The trap

⚠️ The Deputy profile says what you can do; your department says what you can do it on. Two deputies attached to different departments hold exactly the same rights and do not see the same content, groups or statistics. Before concluding that an access is missing, check that you are looking at the right perimeter.

Where to start

1. Run the whole chain once: create a capsule, link it to a track, distribute to a test group, then check from a learner account.
2. Map the existing groups. You will distribute onto them every day and knowing who sits in each one prevents audience mistakes.
3. Review the accesses in your perimeter/department: who holds which profile, and why.

⚠️ Check the audience before every notification. You can notify everyone, so a mistaken group will be noticed immediately, and by a lot of people.

Going further

• Assigning rights: the move you will make most often, profile by profile.
• Understanding structure and permissions: departments, groups and rights, and how they interact.
• Understanding distribution: the three models that decide who sees what.
• Why can’t I see this feature?: the first thing to check before opening a ticket.