Guides
Role vs. permission
In Aligia there are three levels that are often confused: job role, role in the project and access – only the role in the organization and access are technically enforced.
Level 1: Job role (descriptive)
Section titled “Level 1: Job role (descriptive)”The roles in this chapter – project manager, team lead, engineer etc. – describe what someone does in the company. Aligia does not know them as a setting. They are not asked for at invitation and give no access. Details such as position, supervisor or company role in the employee master data are purely descriptive as well.
Level 2: Role in the project (descriptive, with access)
Section titled “Level 2: Role in the project (descriptive, with access)”In the „Ressourcen“ (Resources) tab of a project (see Resources) you assemble the project team. Every entry is a project member:
- Role – free text, e.g. „Elektroplanung“ or „Bauleitung“, plus an optional description.
- Lead flag – marks the lead of a team or of the project.
- Team hierarchy – project members can be subordinated to one another.
- Staffing – a role can be unfilled at first and only describe the required skills; an employee is assigned later.
The role itself is free text and only describes. Two entries do give access, though: a project member with a role and a linked employee gets “Editor” on the project, and the leader entered on a project, program or portfolio gets “Lead”. Risk owners get no access.
Level 3: Role and access (technically enforced)
Section titled “Level 3: Role and access (technically enforced)”Two things count technically.
The role in the organization: owner (whoever created the organization), admin, member or guest. Owners and admins manage settings, members, teams and grants through the role. For data the role gives nothing.
The grant at a place: you may do something at a place if a grant on that place lists it in its access profile. Places are the whole organization, units, portfolios, programs, projects and drives. A grant is for a person or a team and also covers everything below the place, except at restricted places. Base access is such a grant on the whole organization for the team “All members”.
An account is only created by invitation and belongs to exactly one organization. Sign-in is via magic link or passkey (see Access & invitation).
What follows from this
Section titled “What follows from this”- Without a grant you see almost nothing. Only your own entries without a place (such as the timer) and the lookup lists such as skills and project types. Everything else needs a grant or base access.
- Admins need a grant for data too. Whoever creates the organization gets “Full access” on the whole organization for that.
- Guests never do more than the guest list allows, and get grants only on single projects or drives. Base access never reaches them.
- AI conversations and your own runs are private. Polaris and agent chats are visible only to whoever started them.
- Polaris can never do more than you. Aligia checks every action of Polaris or a workflow against your current grants. You use Polaris and workflows through base access or another grant on the whole organization.
- Approving is a question of access. Anyone whose grant at the project allows it may approve times or budget requests. Who should do it is up to your company, typically the team lead or project manager.
The whole rule with all exceptions is in Access: who may do what.