Team modules

What it is

Team Modules is where an admin decides what each teammate can use, and what they can do inside it. Pick a person, tick the modules they need (Estimating, Programme, Manufacturing, Workshop, Invoices and so on) and, within each, the actions they may take. The same list governs the pages they see in the nav, the API behind those pages, and what the assistant will do when that person asks it, in chat, in a connected app, or in an automation they set up.

Admins, the account owner and site admins always have everything and cannot be restricted.

Before you start

• You need to be an admin. The page is admin-only; everyone else is sent back to the dashboard.
• The people must already be in your organisation. Invite them from the Teams page and they appear here.
• A module with a tier badge also needs the subscription plan that includes it. You can tick it now; it becomes usable once the organisation upgrades on Billing.

How to

Choose what a teammate can use

1. Pick the person in the list on the left. Admins are shown with a shield and "Admin · full access" and cannot be selected.
2. Start from a preset if you like: Estimator, Builder, Project Manager or Full access. A preset ticks modules; it says nothing about the assistant.
3. Tick an area's switch to turn the module on. Within it, tick the actions they may take. Ticking any action turns the module's View on; unticking View switches the whole module off. Core areas (Projects, Estimating, Contacts, Organisation) are always on to view.
4. Actions marked with a lock are admin-only (approving and paying payment runs, payee bank details, organisation settings) and cannot be ticked for anyone else.

Changes save as you make them; the corner shows Saving… then Saved. The summary on the right says in plain words what the person can now do and how many modules are on.

Decide what the assistant may do for them

1. Scroll to the Assistant (chat) section. By default the assistant can do for a person anything their modules allow, which is how it has always worked.
2. Untick an area or an action to stop the assistant doing that for this person, even when they ask. The summary names what you switched off.

The assistant never holds the admin-only actions for a non-admin, whatever is ticked.

Open a teammate from the Teams page

1. On the Teams page, a member's row links here with that person already selected.

What happens on its own

• Every tick is enforced server-side as soon as it saves: the nav hides the pages, the API refuses the calls, and the assistant declines the actions. A typed URL to a module that is off shows a notice naming the module and this page.
• The assistant can read this grid and, when an admin asks it in chat, tick or untick for a teammate. It saves the same way the editor does.
• New teammates start with a default set of modules. Modules not yet ready for launch may be hidden from the catalogue; a person's grant for one is kept untouched.

Things that surprise people

• There is no Save button. Each change saves a moment after you make it. If the corner says Save failed, change something again to retry.
• You cannot restrict an admin. Make them a member first on the Teams page, then set their modules.
• Ticking a module with a tier badge does not grant access until the organisation is on that plan. The tick is kept and takes effect on upgrade.
• Switching a module off removes every action inside it. Switch it on again and re-tick what the person needs.
• An automation a person set up runs with their permissions, not the admin's. Take a module away and their automation that used it stops.

Related

• Billing for the plan that unlocks badged modules.
• Teams to invite people and set who is an admin.