Skip to main content
Theme

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

RoleCanCannot
OwnerEverything 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.
OperatorEverything 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.
ViewerSee 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

TaskViewerOperatorOwner
See migrations, plans, checks, decisions and historyYesYesYes
Start a migration, connect a site and give its keysNoYesYes
Carry on, stop, check again, roll back or close a migrationNoYesYes
Remove the keys, or replace oneNoYesYes
Move a migration from your Personal workspace into the agencyNoYesYes
Change the plan: Transform settings, what to copy, fixes, accepting missing files and peopleNoYesYes
Accept the AI's proposals, ask the AI, and Find out more on a jobNoYesYes
Read the questions others asked the AIYesYesYes
Launch: the final sync, the watch, the nightly sync, the checks on the new site, ticking To do jobs, and pushing them to TeamworkNoYesYes
Make a reportNoYesYes
Download a report already made, and download lists as CSVYesYesYes
See who is in the agencyYesYesYes
See the agency's Activity: who did what, and whenYesYesYes
Add people, send an invitation again, remove people, change rolesNoNoYes
Reopen a closed migration, and close one before its domain movedNoNoYes
Delete a migration: it leaves the list, and its keys and copies are destroyedNoNoYes
Connect GitHub from the page GitHub returns you to after installing the App (operators connect it on a migration's Destination step)NoNoYes
Disconnect a GitHub organization from the agencyNoNoYes
Open Settings: see whether GitHub is connected, and your own saved Teamwork keyYesYesYes
Agency nameThere 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.

ActionLeast role
List the workspaces you belong toViewer
List the platforms a site can move fromViewer
See the migrations listViewer
Report a problemViewer
Open a migrationViewer
Read a migration's Transform settingsViewer
Download a report already madeViewer
See the page screenshots the checks tookViewer
See the picture of the old site's home page on the Website address stepViewer
Read the questions asked about a migrationViewer
See who is in the agencyViewer
See the workspace's Activity: who did what, and when, and download it as CSVViewer
See whether you have saved a Teamwork key, and for which site (never the key)Viewer
Forget your own saved Teamwork keyViewer
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 keyOperator
Give a file with a site's key, such as a WordPress exportOperator
Test a connection to a siteOperator
Read what a site holdsOperator
Run the pre-flight checks of the old siteOperator
Check the old site again on a migrationOperator
Start a migrationOperator
Save Transform settingsOperator
Save Transform choices as they are madeOperator
Rebuild the collection pages from the source's pages, keeping the rest of the readOperator
Send a long list in pieces, such as many Transform settingsOperator
Add a file, such as form submissions or redirectsOperator
Turn a dry run into a migrationOperator
Move a migration again to another instance, with its decisionsOperator
Run a migration again with the latest fixes, onto the same instance, with its decisionsOperator
Choose what the load copiesOperator
Apply a fix to the planOperator
Ask the AI to propose table namesOperator
Ask the AI to propose an Insites form in place of a form from another serviceOperator
Ask the AI to review the forms before the loadOperator
Load the destinationOperator
Carry on a nightly sync that is waiting, with a choice for each changed tableOperator
Stop a migrationOperator
Carry on from where it stoppedOperator
Run the checks againOperator
Copy one row or file againOperator
Keep the new site's version of a code file, or copy the old site's version againOperator
Check one code file again, or every one listed, without running the whole VerifyOperator
Point links in records and code at the copies the new site serves, and check the links againOperator
Accept a file as missingOperator
Accept an item a check lists, with a reasonOperator
Accept a person's account as it isOperator
Roll back a loadOperator
Make a reportOperator
Ask the AI about a migrationOperator
Find out more on every open To do job at onceOperator
Find out more on a To do jobOperator
Ask AI to suggest a fix for a checkOperator
Use or put aside a suggested fixOperator
Tick a To do jobOperator
Check a ticked domain or DNS job againOperator
Choose a Teamwork project for the To do listOperator
Choose a Teamwork task listOperator
Choose a Teamwork task, at any depth, to put the jobs underOperator
List the people of a Teamwork project, to assign the watch's tasks toOperator
Choose or stop the Teamwork task list the watch files its problems inOperator
Push the To do list to Teamwork, and save your Teamwork key for next timeOperator
Install the Insites GitHub App, or sign in to GitHub to connect an organization where it is installedOperator
Connect a GitHub organization to the account, once GitHub confirms you can see itOperator
List the repositories the GitHub App can reachOperator
List a repository's branchesOperator
Check where the code goes on GitHub, before the migration startsOperator
Choose where a migration's code goes on GitHubOperator
Stop sending a migration's code to GitHubOperator
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 offOperator
Add a site account the checks sign in withOperator
Remove a site accountOperator
Change a site account, signing it in on the old site againOperator
Sign a site account in on the old site againOperator
Check one site account's signed-in pages again, after VerifyOperator
Skip the signed-in checks, or take that backOperator
Start the final syncOperator
Count the changes of a final sync againOperator
Check the old site for changesOperator
Run the checks on the new siteOperator
Check the source code's age and files against the linked repository againOperator
Check the new site's module versions againOperator
Mark a cutover step doneOperator
Turn on the emails and outside connections held until cutoverOperator
Turn the watch on or offOperator
Turn the nightly sync on or offOperator
Replace a keyOperator
Remove the keysOperator
Close a migrationOperator
Move a migration from your Personal workspace into an agency where you are an owner or operatorOperator
Reopen a closed migrationOwner
Delete a migration. In a Personal account, its personOwner
Connect a GitHub organization to the account from the page GitHub returns you to after installing the AppOwner
Add past enquiries to the CRM: preview, then link each enquiry to its CRM contactOwner
Disconnect a GitHub organization from the accountOwner
Add a personOwner
Send an invitation againOwner
Change a person's roleOwner
Remove a personOwner
Create an agencyInsites staff only
See the sign-ups waiting for approvalInsites staff only
Approve a sign-upInsites 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.