Invite your team
Adding people, what each role can do, and the one ordering detail that trips everyone up.
Go to Members in the Management group, enter an email address, pick a role, and send.
Log in first, invite second
This is the one thing worth getting right.
Nalaras decides once, at the moment you invite, how to reach someone:
- If they already have an account, the invitation appears on the notification bell inside the app. Nothing is emailed.
- If they do not, the invitation is emailed to them.
So if you create an account for a colleague and invite them before they have ever signed in, the invite goes down the email path even though they are about to be sitting in the app. Have them sign in once first, then invite — the invitation is waiting on their bell when they arrive.
What each role can do
| Owner | PM | Designer · Developer · QA | Client | |
|---|---|---|---|---|
| View, comment | ✓ | ✓ | ✓ | ✓ (portal) |
| Create & edit tasks | ✓ | ✓ | ✓ | |
| Manage lists / columns | ✓ | ✓ | ✓ | |
| Invite & manage members | ✓ | ✓ | ||
| Edit roles & permissions | ✓ | ✓ | ||
| Project settings, integrations | ✓ | ✓ | ||
| Client reports | ✓ | ✓ | ||
| Billing | ✓ | |||
| Delete the project | ✓ |
Designer, Developer and QA are the same permission set with different names. They own the board they work on — creating and renaming lists included — but not the project.
Client is different in kind: a client sees the client portal, not the dashboard, and only the tasks marked client-visible.
Changing someone's role
From Members, use the dropdown on their row. Four rules apply:
- You cannot change your own role — ask another Owner.
- Only an Owner can grant Owner.
- Only an Owner can change an Owner's role.
- You cannot grant a permission you do not hold yourself.
A project always keeps at least one Owner. If you are the only one, Nalaras will not let you demote yourself — transfer ownership first.
Custom roles
On Pro, you can build your own roles in Roles & access with any combination of permissions, and rename or hide the built-in ones you do not use. You can also grant a built-in role something it does not have by default — handy when your Developers should be allowed to write client reports, for instance.