Reference
Roles
In an agency, each person has one role: owner, operator or viewer. The role decides what they can do. This page lists exactly what each role can and cannot do, taken from what the tool itself allows.
The three roles
| Role | Can | Cannot |
|---|---|---|
| Owner | Everything an operator can. Also: add people, send an invitation again, remove people, change anyone's role, and delete a migration. | Remove or demote the last owner. Every agency keeps at least one. |
| Operator | Everything a viewer can. Also: start, plan, load, check, roll back, stop, carry on and close migrations; accept the AI's proposals; ask the AI; finish the cutover jobs; make reports. | Add or remove people, change anyone's role, or delete a migration, even one they started. |
| Viewer | See every migration in the agency, with its plan, checks, decisions and history. Download reports that were already made. Copy and download lists as CSV. Read questions others asked the AI. See who is in the agency. | Change anything. A viewer cannot start, change, stop or close a migration, ask the AI, or make a report. Good for a client, or a manager who signs off. |
By task
| Task | Viewer | Operator | Owner |
|---|---|---|---|
| See migrations, plans, checks, decisions and history | Yes | Yes | Yes |
| Start a migration, connect a site and give its keys | No | Yes | Yes |
| Carry on, stop, check again, roll back or close a migration | No | Yes | Yes |
| Remove the keys, or replace one | No | Yes | Yes |
| Move a migration from your Personal workspace into the agency | No | Yes | Yes |
| Change the plan: Transform settings, what to copy, fixes, accepting missing files and people | No | Yes | Yes |
| Accept the AI's proposals, ask the AI, and Find out more on a job | No | Yes | Yes |
| Read the questions others asked the AI | Yes | Yes | Yes |
| Launch: the final sync, the watch, the nightly sync, the checks on the new site, ticking To do jobs, and pushing them to Teamwork | No | Yes | Yes |
| Make a report | No | Yes | Yes |
| Download a report already made, and download lists as CSV | Yes | Yes | Yes |
| See who is in the agency | Yes | Yes | Yes |
| See the agency's Activity: who did what, and when | Yes | Yes | Yes |
| Add people, send an invitation again, remove people, change roles | No | No | Yes |
| Reopen a closed migration, and close one before its domain moved | No | No | Yes |
| Delete a migration: it leaves the list, and its keys and copies are destroyed | No | No | Yes |
| Connect GitHub from the page GitHub returns you to after installing the App (operators connect it on a migration's Destination step) | No | No | Yes |
| Disconnect a GitHub organization from the agency | No | No | Yes |
| Open Settings: see whether GitHub is connected, and your own saved Teamwork key | Yes | Yes | Yes |
| Agency name | There is nothing to change. Insites names the agency when it sets it up. | ||
A button you cannot use for your role is shown greyed, with the reason beside it, for example Viewers cannot ask AI. Ask an owner or operator.
Your Personal workspace
Your Personal workspace has one person in it: you, as its owner. There are no roles to change and no one to add, so the People page shows no role controls there. You started every migration in it, and you can delete any of them. A new Personal workspace can have one migration going at a time until Insites approves it.
You can move a migration from your Personal workspace into an agency where you are an owner or an operator. A viewer in an agency cannot move one into it. See Moving a migration into an agency.
Insites staff
Insites staff are recognized by the domain of their email address (insites.io). Nothing else marks them, so a person with an address on that domain is staff. Staff can:
- Create an agency, and add its first owner.
- Change the role of anyone in any agency, without being a member of it. The same rules apply: the last owner cannot be demoted, and the change is recorded.
- Approve a new Personal workspace, so it can have more than one migration going. The Sign-ups page, in the menu on the left for staff only, lists everyone waiting, newest first, with Approve on each row and who approved whom lately. The Approve link in the sign-up email does the same. Either way the person is emailed and the approval shows on Activity.
- Read the Activity of any workspace, without being a member of it, to help.
- Go ahead with a load or a roll back while another migration works on the same destination. This is recorded with who did it.
- Have more than one migration going at once in their own Personal workspace, without waiting for approval.
To see an agency's migrations, staff need to be added to that agency like anyone else. A member who is staff also sees the migrations that were deleted, marked deleted with who deleted them and when. Being staff does not let a person delete a migration: that takes the owner role in the account.
Changing someone's role
- Who can: an owner of the agency, and Insites staff.
- How: on the People page, choose the new role in the person's row. The tool says what the person can then do, and changes the role only when you confirm.
- The last owner: an agency always keeps at least one owner. If you are the only one, your Change role button is greyed and says why. Make someone else an owner first.
- People who have not signed in yet: their role can be changed too. It applies when they sign in. The invitation they were already sent still names the old role.
- When it takes effect: on the person's next action in the tool. They do not need to sign out. Anything they already started stays theirs.
- The record: every change is written to the audit trail: who changed it, whose role it was, the old role, the new role, and when. Everyone in the agency sees it on Activity.
- No email: the person is not emailed about the change.
- Adding someone already in the agency does not change their role. The tool refuses and says to change their role instead.
How an invitation sets a role
An owner adds a person on the People page with their email address and a role: operator, viewer or owner. The person is added with that role straight away, and emailed an invitation with a sign-in link that names the role. If the invitation is lost or its link runs out, Send invite again sends a new one with the person's current role. Adding the same person again with the same role sends the invitation again only if the first one never went.
Every action, and the role it needs
Each thing the tool can do, and the least role that can do it. This list is checked against the tool on every change, so it stays correct.
| Action | Least role |
|---|---|
| List the workspaces you belong to | Viewer |
| List the platforms a site can move from | Viewer |
| See the migrations list | Viewer |
| Report a problem | Viewer |
| Open a migration | Viewer |
| Read a migration's Transform settings | Viewer |
| Download a report already made | Viewer |
| See the page screenshots the checks took | Viewer |
| See the picture of the old site's home page on the Website address step | Viewer |
| Read the questions asked about a migration | Viewer |
| See who is in the agency | Viewer |
| See the workspace's Activity: who did what, and when, and download it as CSV | Viewer |
| See whether you have saved a Teamwork key, and for which site (never the key) | Viewer |
| Forget your own saved Teamwork key | Viewer |
| See whether sending the code to GitHub is on, and which GitHub organizations the account connected (never a token) | Viewer |
| After installing the Insites GitHub App, see which installations your own GitHub sign-in can see (nothing is connected) | Viewer |
| Tell the tool the page stopped waiting for an action (sent by the page itself, never typed) | Viewer |
| Give a site's key | Operator |
| Give a file with a site's key, such as a WordPress export | Operator |
| Test a connection to a site | Operator |
| Read what a site holds | Operator |
| Run the pre-flight checks of the old site | Operator |
| Check the old site again on a migration | Operator |
| Start a migration | Operator |
| Save Transform settings | Operator |
| Save Transform choices as they are made | Operator |
| Rebuild the collection pages from the source's pages, keeping the rest of the read | Operator |
| Send a long list in pieces, such as many Transform settings | Operator |
| Add a file, such as form submissions or redirects | Operator |
| Turn a dry run into a migration | Operator |
| Move a migration again to another instance, with its decisions | Operator |
| Run a migration again with the latest fixes, onto the same instance, with its decisions | Operator |
| Choose what the load copies | Operator |
| Apply a fix to the plan | Operator |
| Ask the AI to propose table names | Operator |
| Ask the AI to propose an Insites form in place of a form from another service | Operator |
| Ask the AI to review the forms before the load | Operator |
| Load the destination | Operator |
| Carry on a nightly sync that is waiting, with a choice for each changed table | Operator |
| Stop a migration | Operator |
| Carry on from where it stopped | Operator |
| Run the checks again | Operator |
| Copy one row or file again | Operator |
| Keep the new site's version of a code file, or copy the old site's version again | Operator |
| Check one code file again, or every one listed, without running the whole Verify | Operator |
| Point links in records and code at the copies the new site serves, and check the links again | Operator |
| Accept a file as missing | Operator |
| Accept an item a check lists, with a reason | Operator |
| Accept a person's account as it is | Operator |
| Roll back a load | Operator |
| Make a report | Operator |
| Ask the AI about a migration | Operator |
| Find out more on every open To do job at once | Operator |
| Find out more on a To do job | Operator |
| Ask AI to suggest a fix for a check | Operator |
| Use or put aside a suggested fix | Operator |
| Tick a To do job | Operator |
| Check a ticked domain or DNS job again | Operator |
| Choose a Teamwork project for the To do list | Operator |
| Choose a Teamwork task list | Operator |
| Choose a Teamwork task, at any depth, to put the jobs under | Operator |
| List the people of a Teamwork project, to assign the watch's tasks to | Operator |
| Choose or stop the Teamwork task list the watch files its problems in | Operator |
| Push the To do list to Teamwork, and save your Teamwork key for next time | Operator |
| Install the Insites GitHub App, or sign in to GitHub to connect an organization where it is installed | Operator |
| Connect a GitHub organization to the account, once GitHub confirms you can see it | Operator |
| List the repositories the GitHub App can reach | Operator |
| List a repository's branches | Operator |
| Check where the code goes on GitHub, before the migration starts | Operator |
| Choose where a migration's code goes on GitHub | Operator |
| Stop sending a migration's code to GitHub | Operator |
| Send the moved code to GitHub, on a new branch with a pull request. Refused with a 409 ("This is coming soon") while the send is switched off | Operator |
| Add a site account the checks sign in with | Operator |
| Remove a site account | Operator |
| Change a site account, signing it in on the old site again | Operator |
| Sign a site account in on the old site again | Operator |
| Check one site account's signed-in pages again, after Verify | Operator |
| Skip the signed-in checks, or take that back | Operator |
| Start the final sync | Operator |
| Count the changes of a final sync again | Operator |
| Check the old site for changes | Operator |
| Run the checks on the new site | Operator |
| Check the source code's age and files against the linked repository again | Operator |
| Check the new site's module versions again | Operator |
| Mark a cutover step done | Operator |
| Turn on the emails and outside connections held until cutover | Operator |
| Turn the watch on or off | Operator |
| Turn the nightly sync on or off | Operator |
| Replace a key | Operator |
| Remove the keys | Operator |
| Close a migration | Operator |
| Move a migration from your Personal workspace into an agency where you are an owner or operator | Operator |
| Reopen a closed migration | Owner |
| Delete a migration. In a Personal account, its person | Owner |
| Connect a GitHub organization to the account from the page GitHub returns you to after installing the App | Owner |
| Add past enquiries to the CRM: preview, then link each enquiry to its CRM contact | Owner |
| Disconnect a GitHub organization from the account | Owner |
| Add a person | Owner |
| Send an invitation again | Owner |
| Change a person's role | Owner |
| Remove a person | Owner |
| Create an agency | Insites staff only |
| See the sign-ups waiting for approval | Insites staff only |
| Approve a sign-up | Insites staff only |
A few things need no role because they are not done by a person in a workspace: the tool's own scheduled work, a migration asking for its next step, the version check after a deploy, and the Approve and AI limit links Insites staff are emailed. Each has its own lock.