Roles and permissions

Rectify has three roles: Account Owner, Member and Assignee. The first two run the organisation. The third is scoped to the work handed to them.

The role someone holds decides what they can see, not just what they are allowed to press. That is the part worth reading twice, because it explains most of what people find surprising.

The short version

• Account Owner. One person. Everything a member can do, plus the decisions that cost money or change the organisation itself.
• Member. The full run of the work: projects, snags, assignees, sign-off.
• Assignee. Sees the projects they have been given work in, and only their own snags inside them.

Who can do what

Action	Owner	Member	Assignee
See every project and snag in the organisation	✓	✓	✕
See the snags assigned to them	✓	✓	✓
See the details of a project they have work in	✓	✓	✓
See other people’s snags in that project	✓	✓	✕
Create, edit and delete projects	✓	✓	✕
Add, edit and delete snags	✓	✓	✕
Assign a snag	✓	✓	✕
Invite an assignee	✓	✓	✕
Add photos and notes to a snag	✓	✓	✓ ¹
Mark a snag resolved	✓	✓	✓ ¹ ³
Close a snag	✓	✓	✕
Send a snag back, or reopen it	✓	✓	✕
Move a due date	✓	✓	✕
Request a due-date extension	✕ ²	✕ ²	✓ ¹
Approve or decline an extension	✓	✓	✕
Add or remove team members	✓	✕	✕
Rename the organisation	✓	✕	✕
Change the plan and buy seats	✓	✕	✕

✓ can do this. ✕ cannot. ¹ On the snags assigned to them, and only those. ² Owners and members do not ask for extra time, they move the due date themselves. ³ With a note saying what they have done.

What a member can do

A member is a project manager in every practical sense: the whole organisation is visible to them, and the work of running it is theirs. Projects, snags, assignments, sign-off and the answer to an extension request all sit with the member who is closest to the job.

What a member cannot touch is the account itself. They cannot add or remove team members, rename the organisation, or change the plan. A member who hits a plan limit can see exactly what has run out and can do nothing about it, so the fix is with the owner.

What the Account Owner can do

The Account Owner does everything a member does, and holds the decisions that cost money or change the shape of the account: the team roster, the organisation’s name, the plan, and the billing behind it.

There is one owner, and an organisation always keeps one. The owner cannot remove themselves.

Plan and seat changes happen in the billing portal at web.rectifyapp.co, signed in as the owner, rather than in the iOS app. See Adding more seats for what that costs part way through a billing period.

What an assignee can do

An assignee is usually a subcontractor or a trade: someone you hand defects to without giving them the run of your account.

What they see is the snags assigned to them, and enough of the project around those snags to know which job they are on: its name, its photo and its description. What they do not see is the rest of that project. Other people’s snags in it are invisible to them, as is any project they hold no work in, and so is everything else in the organisation.

On a snag that is theirs, an assignee adds photos and notes, moves it forward as far as resolved, with a note saying what they have done, and can ask for more time on the due date. A request that is still waiting on an answer can be withdrawn.

Everything else is closed to them. An assignee cannot create projects or snags, cannot assign work, cannot move a due date themselves, and cannot close anything.

Assignees do not take a seat. They are not billed as team members are, which is why handing work to ten trades does not cost what adding ten members does. Free allows up to five assignees, and Team, Pro and Personal have no limit. See Assignee limit reached for what counts towards the five.

Why an assignee cannot close a snag

This is the one people trip over, and it is deliberate.

An assignee marks a snag resolved when they have done the work. Closing it is a separate decision, and it belongs to your organisation: the owner or any member checks the work against what was logged, then closes it. The person who did the work cannot sign it off, including when that person is you.

The effect is that nothing leaves your list on the assignee’s word alone. Logging your first snag covers what each stage means and what stays attached for handover.

Adding people

These are two different actions with two different answers, and mixing them up is the usual reason someone cannot find the option they were told about.

Adding a team member takes a seat and is therefore owner only. If you are a member, you will not see it. Send whoever holds the account to Adding more seats.

Adding an assignee takes no seat, and any member can do it as well as the owner. That is the one to reach for when you need somebody working on defects rather than running projects.

What costs a seat

Only members. On Team and Pro you pay per seat, and a seat is one member of your organisation:

• The owner is a member too, so they use a seat. On Free, the one seat is yours.
• A member uses one seat, however many projects they work on and however many snags are assigned to them.
• An invitation uses a seat as soon as it is sent, not when it is accepted. You need a spare seat to send it.
• Assignees never use a seat, on any plan, and are never billed. Inviting one costs nothing.
• Personal has no seats. It is one price for you and one other person in your household, and that limit is fixed. See The Personal plan.

Seats are bought in advance: the owner chooses how many to pay for, and the organisation can have that many members. Adding a member when every seat is in use means buying another first. Adding more seats covers how, and what it costs part way through a billing period.

If someone who is already an assignee needs to run projects, the owner can invite them as a member. They move across rather than being in the organisation twice: they use a seat from then on, and stop counting as an assignee.

If your subscription lapses, every member except the owner is suspended until the owner reactivates them, and a suspended member does not use a seat.

If someone cannot do something you expected

Worth checking, in this order:

• Which role they actually hold. An assignee who was described as being “on the team” is still an assignee. Being able to see the project does not mean they can see the snags in it that are not theirs
• Whether the action is owner only. Seats, the plan, the organisation name and removing team members all are
• Whether they were added as an assignee when a member was intended. The fix is a member invitation from the owner, not a change to their assignee access

If none of that explains it, tell us what the person was trying to do, what happened instead, and the email address they signed in with.