How permissions work
Understand how templates grant access at each level.
What you can do in Teralo is set by your permission template: a named set of permissions, such as Site Team or View Only. You hold one template in each organisation you belong to and one on each project you're on. The template decides which tools you see and what you can do in each. Your job title grants nothing.
- Organisation permissions and project permissions are two separate lists. An organisation template covers the organisation's own tools and settings, and a project template covers one project.
- The two templates don't affect each other, and your project template can differ from project to project.
- Everyone has a template at each level. When none has been chosen, Teralo uses No Access, which grants nothing.
Learn more about organisation level and project level.
In the template editor, permissions are grouped by module, with a row for each tool and four columns: View, Add, Edit and Delete. Some tools have extra rows for one job, such as Approve bookings or Review submittals. The AI Chat and Host AI allowance rows have a single Allow switch.
A tool appears in your sidebar when your template holds any permission on its row.
- Ticking a column ticks every column to its left in the row, and unticking a column unticks every column to its right. So a template that can add or edit a tool's records can always view them.
- The Progress Claims and Variations rows have no View column, and their columns are independent: ticking approve doesn't give the right to submit.
- Delete is never included by another permission. On most tools a person can manage records without being able to delete them. Calendars and passive fire have no separate delete permission, so managing them includes deleting.
- Organisation administrators have every permission in their organisation and on every project it hosts, whatever their template. On a project another organisation hosts, an administrator is a guest with a template like anyone else.
- Project administrators have every permission on their project. The person who creates a project becomes one, and more are added under Project Administrators in the project settings. A project administrator from a guest organisation has only their template.
- Meeting attendees can open the meetings they attend, and a whiteboard can be shared with one person.
A tool that an enterprise agreement withholds from the host doesn't appear on its projects for anyone, administrators and guests included, and no template can grant it. Learn more about plans and entitlements.
- Which rows a guest sees. A permission decides whether a guest can open a tool, and which records they see in it is fixed for each tool. Permissions marked for host staff only have no effect on a guest. Learn more about hosts and guests.
- Who acts on a workflow step. On most tools you need to be assigned to the step and hold the tool's approval permission. On some, a manage permission lets you act on any step. Learn more about assigning approvers.
- Select your name at the bottom of the sidebar, then Account.
- Your organisations show your template after Role, and the Projects card shows your template on each project.
Only the template's name shows there. Host staff with Can view project permission templates and assignments can open a project's templates and see what each one grants. Learn more about permission templates.
Only the host can change your template on a project. Teralo emails you when it does. The new permissions apply from your next action, and your sidebar updates when you next load a page.
- Check that you're on the project you expect. Your template can differ between projects.
- Check whether the tool is for host staff only: project Settings, Tools and Permissions, Reports, Procurement and Cashflow, and inside a contract the budget, payments and direct costs. A guest never sees these.
- Ask the host to add the tool to your template, or to move you to another template.
- If nobody on the project can see the tool, the host's plan may not include it.