How to manage people’s roles in Perno Company

Each person in Perno Company is assigned a role that determines their access to modules and administrative actions. Roles let you match colleagues’ permissions to their responsibilities, whether they manage the organisation, deliver projects, handle sales or recruitment, or work on tasks. Below you will find instructions for changing a role and a description of the permissions available to each role.

How to manage people’s roles in Perno Company

1. Go to Perno Company

At the top of the screen, open the Context menu and select Perno Company.

The role applies to the selected Perno Company organisation. It does not automatically grant the same permissions in Perno Store, Perno Orchestration or another organisation.

2. Open the colleagues list

In the menu on the left, click Colleagues.

The list shows:

• Colleague — the colleague;

• Role — their assigned role;

• Status — their access status, for example Active;

• Actions — the available actions.

Account owner and Company admin can manage colleagues’ roles, subject to the restrictions concerning the account owner.

The Invite colleague button starts the process of inviting a new person to the organisation.

3. Change a colleague’s role

1. Find the person in the Colleagues list.

2. In their row, click Role.

3. On the Change colleague role page, open the Role dropdown.

4. Select the appropriate role:

• Company admin;

• Company manager;

• Project manager;

• Sales manager;

• HR manager;

• Company member.

5. Click Save role to save the change.

6. In the Colleagues list, check the role assigned to that person.

Account owner is not an option in the selection list shown. The role change form is not used to transfer ownership of the organisation.

4. Understand each role’s permissions

Account owner

The account owner has the highest level of access. They can:

• use all Perno Company modules;

• manage colleagues and their roles;

• manage clients, contacts and projects;

• access all non-private tasks and projects;

• manage tasks, workflows, Board and Backlog;

• manage time entries and Roadmap;

• use CRM leads, pipelines, activities, email and reports;

• configure sales process stages and sources;

• use People Pool;

• manage OKRs and NPS surveys;

• manage integrations and automations;

• manage platform subscriptions and billing;

• access the account’s API token;

• manage company settings reserved for the owner;

• manage Perno Orchestration and merchant accounts, where applicable to the account.

Private tasks created by another person remain inaccessible even to the account owner. A private CRM mailbox is available to the user who connected it.

Company admin — organisation administrator

The administrator is responsible for the organisation’s day-to-day management. They can:

• manage colleagues and their roles;

• access all non-private projects and tasks;

• create and manage clients, contacts and projects;

• manage project membership;

• manage tasks, workflows, time entries and Roadmap;

• use CRM, reports, email, signatures and sequences;

• configure sales process stages and sources;

• use People Pool;

• manage OKRs and NPS surveys;

• manage the organisation’s integrations and automations;

• use administrative imports and bulk actions.

The administrator cannot:

• view another person’s private tasks or private CRM mailbox;

• change the account owner’s role, deactivate them or remove them;

• remove their own membership in the organisation;

• manage billing and subscriptions reserved for the owner;

• access the owner’s API token;

• take ownership of the organisation.

Company manager — organisation manager

Company Manager has broad access to Perno Company and can manage most areas in the same way as Company Admin. This role is suitable for managers who need to coordinate the company’s daily operations but should not have access to every project.

A Company Manager can use CRM, manage clients and contacts, work with OKRs, People Pool and other company tools. However, access to project-related information is limited to projects to which the person has been assigned.

This means that a Company Manager can only see and manage:

• assigned projects;

• tasks belonging to those projects;

• related roadmap items;

• time entries connected with those projects.

Projects and related data that are not assigned to the Company Manager remain unavailable, including through direct links and the Perno API.

Choose this role for operational managers who require extensive company-management capabilities while keeping private or unrelated project information restricted.

Project manager

The project manager is responsible for project delivery and managing working time. They can:

• access the clients and projects area;

• create and edit projects;

• manage project membership;

• work with tasks in projects to which they have been added;

• create, edit, assign, move and delete accessible tasks;

• plan projects on Roadmap;

• view and manage time entries;

• add time entries from Time logs;

• view the team’s task timeline.

The project manager cannot manage colleagues or their roles. They do not automatically gain access to projects to which they have not been added or to other people’s private tasks.

They do not have access to CRM pipelines and reports, NPS, sales process configuration, People Pool, OKR management or the organisation’s integration management.

Sales manager

The sales manager is responsible for clients, sales opportunities and related communication. They can:

• use leads and sales and partner pipelines;

• create and manage leads and sales opportunities;

• manage activities and comments within their permitted scope;

• use CRM reports;

• connect and use their own Gmail mailbox;

• use email signatures and sequences;

• create and manage NPS surveys;

• access, create and edit clients, contacts and projects;

• work with tasks in projects to which they have been added.

The sales manager cannot:

• manage colleagues or their roles;

• configure sales process stages or sources;

• automatically gain access to all projects;

• view other people’s private mailboxes or private tasks;

• manage Roadmap as a project administrator;

• use People Pool;

• manage OKRs;

• manage integrations for the entire organisation.

The exception for integrations is the supported connection to their own Gmail mailbox. Sales process configuration remains available only to Account owner and Company admin.

HR manager

The HR manager is responsible for People Pool. They can:

• use the candidate database;

• add and edit candidates;

• manage CVs and anonymised CVs;

• manage specialisations, keywords and accepted job positions;

• search and filter candidates;

• view the change history for candidate data;

• use basic task features in projects to which they have been added;

• add and edit their own time entries.

The HR manager cannot manage colleagues, roles, clients or projects. They do not have access to projects to which they have not been assigned, or to CRM pipelines and reports or NPS.

They also cannot manage all time entries in the organisation, OKRs, task and sales workflow configuration or the organisation’s integrations.

Company member — organisation member

The organisation member has standard access for working on tasks. They can:

• work with tasks in projects to which they have been added;

• use Board and Backlog;

• create and update accessible tasks;

• move tasks between available workflow stages;

• add comments and mention colleagues;

• log time against accessible tasks;

• edit their own time entries;

• view Roadmap and the task timeline relevant to them.

The organisation member cannot:

• access projects to which they have not been added;

• view other people’s private tasks;

• manage colleagues, roles, clients or projects;

• manage all time entries in the company;

• manage Roadmap;

• use CRM, CRM reports, NPS or People Pool;

• manage OKRs;

• configure workflows or manage the organisation’s integrations.

5. Manage colleagues’ access

In the Colleagues list, the following buttons may be available next to a person:

• Role — change the assigned role;

• Deactivate — deactivate membership and revoke access to the organisation;

• Remove — remove the colleague from the organisation.

The available actions depend on your permissions and the person concerned. The administrator cannot modify, deactivate or remove the account owner, or remove their own membership.

6. Remember the shared access rules

Regardless of the assigned role:

• private tasks are visible only to their creator;

• a private CRM mailbox is available to the person who connected it;

• where comment deletion is restricted to the author, users can delete only their own comments;

• deactivating membership removes access to the organisation;

• task visibility may be further restricted by project membership and active filters;

• permissions apply within a specific organisation.

If a colleague cannot see a task or module, check their role, membership status, project assignment and active filters. Also check whether the task is private.