Skip to main content
Theme

Explanation

Agency workspaces

An agency migrates sites for many clients, with several people on each migration. A workspace is where an agency's migrations live: everyone in it sees the same migrations, plans and reports, and what each person can do depends on their role.

Your own workspace, and agencies

Everyone has their own personal workspace for migrations nobody else needs to see. An agency workspace is shared. The menu on the left always names the one you are working in, under the logo: Personal, or Agency, in purple, with the agency's name and your role and a building icon, so the two are easy to tell apart. Neither is shaded: the only shaded item in the menu is the page you are on. Click it to switch. A migration belongs to the workspace it was started in, not to the person who started it, so it stays with the agency when people change. A link to a migration in another of your workspaces opens it there, and the page says it switched. If the browser remembers a workspace that is not yours, such as one from someone else's earlier sign-in in the same browser, the tool moves you to Personal and says so.

  1. OwnerEverything an operator can, and manages people
  2. OperatorStarts, plans, loads and rolls back migrations
  3. ViewerReads migrations, plans and reports
An agency always keeps at least one owner.

Moving a migration into an agency

A migration you started in your Personal workspace can move into an agency you belong to, so your colleagues can see it and work on it. Open the migration and press Move to agency at the top of the page. If you belong to more than one agency, choose which. The tool says what moves and asks you to confirm. Once it has moved, the page switches to the agency and opens the migration there.

  • Who can: you, for a migration in your own Personal workspace, into an agency where you are an owner or an operator. A viewer in the agency cannot. The button only shows when there is an agency you can move it to.
  • Which migrations: any that is not working right now. A migration that is reading the old site, building its plan, loading, checking or rolling back has to finish, or be stopped, first.
  • What moves: everything the migration holds. Its final and nightly syncs, its keys, its copy of the old site and its plan, its record of the load, its checks and screenshots, its reports, every decision and its history. The keys are encrypted again for the agency, as every key is bound to the account it is in. Nothing of it stays in your Personal workspace except the lines its history left on your Personal Activity, and the agency's Activity gets a copy of them.
  • What the agency brings: some things belong to an account, not to a migration, so once it has moved the migration uses the agency's. Its AI limit is the agency's from its next use of the AI; what it has already used still counts. If the AI limit was raised for your Personal account, that raise stays with Personal. GitHub connections are the agency's own: if the migration was set to send its code to a GitHub organization that only your Personal account connected, that choice is cleared, and the migration's history says so. An owner of the agency connects the organization in Settings, then you choose where the code goes again. Code already sent stays on GitHub. Your saved Teamwork key stays in your Personal account: save it in the agency too and jobs already pushed to Teamwork keep in step from there.
  • One way only: from Personal into an agency. A migration in an agency does not move out again, or into another agency.
  • Who is told: the move is written to the Activity of both: who moved which migration, from where, to where. Nobody is emailed.
  • If it stops part way: nothing is lost. The migration stays where it was, whole, until everything has been copied and checked in the agency. Press Move to agency again to finish.

Roles

Roles lists exactly what each role can do, task by task, with what Insites staff can do.

RoleCanCannot
OwnerAdd and remove people and change their roles, and everything an operator can.Remove the last owner.
OperatorConnect instances, start migrations, change the plan, load, verify, roll back and close.Manage who belongs.
ViewerRead every migration, plan, report and decision.Change anything. Good for a client, or a manager who signs off.

Changing someone's role

The full rules are in Roles. An owner can change the role of anyone in the agency, and of someone who has been invited and has not signed in yet. Open People, and choose a new role in the Role column of that person's row. The tool then says in plain words what the person can do as that role, and changes it only when you confirm.

  • 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 person is not emailed. The change is written to the audit trail with who made it, whose role it was, the old role and the new one, and when, and everyone in the agency can see it on Activity.
  • An agency always keeps at least one owner. If you are the only owner, the Change role button is held, and says why beside it: make someone else an owner first, then change your own role.
  • For someone who has not signed in yet, the new role applies when they do. The invitation they were already sent still names the old role.
  • Adding someone who is already in the agency does not change their role: the tool says so, and the role is changed in their row instead.
  • A Personal account has one owner, you, and no roles to change. Insites staff can change a role in any agency.

Setting one up

  1. Insites sets up the agency: Insites staff open People in the menu on the left, name the agency and create it, and add its first owner.
  2. The owner switches to the agency from the account switcher in the menu on the left, opens People in the menu on the left, and adds each colleague by email with their role.
  3. Each of them is emailed an invitation with a sign-in link. There is no password: they click the link, press Continue, and they are in, with the agency to switch to from the account switcher in the menu on the left.

The People page shows whether each invitation went, and when each person last signed in. Activity, next to it in the menu on the left, keeps the history: who invited, accepted, changed a role or removed someone, and what happened on each migration. See Activity history.

On People, if an invitation is lost or its link has expired, click Send invite again, or they can sign in any time from the sign-in page with the address the invitation went to.

Signing in

Nobody has a password for the Migration Tool. On the sign-in page, enter your email address and the tool emails you a link. It works once, for 15 minutes (an invitation's link lasts three days). The link opens a page with a Continue button rather than signing you in straight away, so the email scanners many companies use cannot spend your link before you do. After that you stay signed in on that device while you keep using it, until a week passes without a visit. Sign out of all devices, in the profile menu at the bottom of the menu on the left, signs you out everywhere.

Anyone can get a link. Someone new to the tool gets Just me, a space of their own, where they can start one migration straight away. Two starts at the same moment, from two tabs or two people, still start only one: the second is told a migration is already under way. Insites lifts that limit after a quick check. People an agency has invited, and Insites staff, have no such limit. The sign-in page says the same thing after every request, so it never reveals who already uses the tool.

What is shared, and what is not

  • Shared: migrations, their plans, checks, reports, To do lists and the record of decisions. Emails about a migration go to whoever started it. Every email the tool sends names, in its small print, the address it went to and the account it is about, with the account's number in brackets, for example Sent to [email protected] for the account Acme Digital (ws-3f9a0c4e7b21d58a6c0e9f13). An agency's number is its workspace ID, which is how Insites finds the agency when you ask for help. Everyone in the agency can find its workspace ID on the People page, under the agency's name, with a button that copies it. A Personal account's number is your email address. When a run fails, or stops getting any further, Insites is emailed too, so it can help.
  • Never shared: keys and passwords. They are encrypted, used only inside the tool, and never shown to anyone, owners included.
  • People outside the agency cannot tell it exists: asking for it answers the same as asking for one that does not.