Reference & Data Model
Access: who may do what
You may do something at a place if a grant on that place allows it. Without a grant you see only your own entries without a place and the lookup lists.
The rule
Section titled “The rule”You may do something at a place if a grant on that place lists it in its access profile. Otherwise you may not.
- Places are the whole organization, units, portfolios, programs, projects and drives. They form a tree: portfolio › program › project, unit › sub-unit. Everything sits under the whole organization.
- A grant is for a person or for a team. A grant to a team counts for every member of the team.
- A grant on a place also covers everything below it, unless that is restricted. At a restricted place only grants on exactly that place or something below it count.
- The access profile says what the grant allows: “Viewer”, “Editor”, “Lead”, “Full access” or a profile of your own organization.
Company data such as companies, products and the organization’s KPIs sit at the whole organization. Employees sit at their unit.
Base access
Section titled “Base access”Base access is one grant on the whole organization for the team “All members”. Every person of the organization except guests is in this team; Aligia keeps its members up to date. An admin sets the level:
| Level | What every member may do |
|---|---|
| Off | Nothing through base access; only grants to people and teams count |
| Company data | View companies, employees, products and KPIs, no projects; use Polaris and workflows |
| View | View everything that is not restricted; use Polaris and workflows |
| Edit | Work everywhere and create projects; use Polaris, workflows and the optimizer |
You use Polaris and workflows through base access or through another grant on the whole organization that allows it.
The exceptions
Section titled “The exceptions”- Your own entries without a place are yours, for example a timer or a task without a project. Only you see and change them.
- Every member reads the lookup lists: skills and skill categories, good types, spec categories, project types, takeaway categories and types, issue labels, equipment units and colleagues’ names. Changing them needs a grant on the whole organization.
- Guests never do more than the guest list allows: view, create and change tasks, issues, structures, files and time; view segments, the project and its members. Guests get grants only on single projects or drives, never on the whole organization, a unit, a program or a portfolio. Base access never reaches them.
- Owners and admins manage through their role the organization’s settings, members, teams and grants. For data they need a grant like everyone else. Whoever creates the organization gets “Full access” on the whole organization for that.
What only owners and admins may do
Section titled “What only owners and admins may do”| Activity | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Invite members, change roles, remove | ✓ | ✓ | – | – |
| Manage base access, teams, access profiles and grants on the whole organization | ✓ | ✓ | – | – |
| View the organization’s audit log and AI usage | ✓ | ✓ | – | – |
| Manage the organization’s credentials (OAuth/API for MCP) | ✓ | ✓ | – | – |
| Change the organization’s settings | ✓ | ✓ | – | – |
| See the member list | ✓ | ✓ | ✓ | – |
Everything else, reading and editing projects, company data and employees included, follows the rule above: it needs a grant, for admins just as for members.
Where grants come from
Section titled “Where grants come from”- Given: someone gives a person or a team a grant at a place.
- Base access: as above, for all members except guests.
- Automatic: whoever creates a project gets “Lead” on it. The leader entered on a project, program or portfolio gets “Lead”, for programs and portfolios also on everything below. A project member with a role and a linked employee gets “Editor” on the project. These grants end when the entry ends.
Where you set it
Section titled “Where you set it”- Give a grant at a place: in Aligia in the “Access” tab of the project, program, portfolio or drive. Anyone whose own grant there allows giving grants (for example “Lead”) may do so, and every admin.
- Restrict a place: in the same tab with “Restrict access”.
- Base access, people, teams, access profiles, explain and audit: in the sign-in service under “Access”, admins only. “Explain” answers: may this person do this at this place, and if not, what is missing?
See also
Section titled “See also”Roles · Private data · Technical accounts · Guides › Role vs. permission