Documentation

Using Go2

How to create short links, manage your team, and understand where your links point.

Getting started

Go2 shortens addresses and runs them through your own name — yourname.go2.education/welcome instead of a long URL. You create a link once and it is served from every address the platform gives you, with one redirect and nothing else in between.

These pages assume you are signed in to the customer console at app.go2.education.

Useful from day one:

  • Links — managing addresses, short names, query parameters.
  • QR codes — posters and print.
  • Sub-accounts — teams, branches, sites under one account.
  • Users and roles — who can do what.
  • Settings — your personal preferences and the account's shared details.

Current constraints

  1. One link per account (and per sub-account) at a time. Creating a second link in the same account returns "Free tier allows one link." Delete or let the current one expire first.
  2. New links expire 30 minutes after creation. The expiry is set when the link is created; edit the link to change it.
  3. Account activation uses a verification link. The link emailed to your address activates the account and expires after 24 hours. If automatic sign-up is disabled, a member of the Go2 team contacts you after you submit the form.

Creating an account

New accounts are created at app.go2.education/signup, with an email address and a password. After that you sign in with the same address and password.

What happens after you submit the form

Automatic account sign-up is currently disabled, so submitting the form registers an interest rather than an account. One of two things then happens:

  • if your account can proceed, a verification link is emailed to the address you submitted. Clicking it activates the account, and you can then sign in with the same address and password. The link expires after 24 hours;
  • otherwise, a member of the Go2 team will be in touch.

Either way, every address is its own account — no two submissions share one.

Passwords

Every route to setting a password applies the same four rules:

  • At least 12 characters.
  • Must contain a symbol.
  • Must not be a common guess (password12345!, admin..., welcome... are rejected).
  • Must not contain your email's local part.

An address like margaret@example.com cannot use a password containing margaret, even inside a longer phrase. If your choice is rejected without a clear reason, this rule is usually why.

Signing in

  • The console is app.go2.education. The admin console admin.go2.education is a separate system — signing in to one gives you nothing on the other.
  • Sessions last eight hours.
  • Signing in over plain HTTP is refused; only HTTPS is accepted for the management console.

After signup you are the account owner of a new account. See Roles for what that means.

QR codes

Every link can be exported as a QR code, drawn entirely in your browser. A code is generated from the link's address on demand; no QR code is stored or sent to us.

Export and style

A code downloads as SVG or PNG. Three controls change the printed result:

  • Foreground colour (module colour).
  • Background colour.
  • Centre mark — the destination's own icon, the first letter of its name, or nothing. The destination's icon is the default centre mark.

The icon is fetched by your browser straight from the destination's website, the way a bookmark icon is. Nothing passes through us and nothing is stored. If the icon cannot be read — for example because the destination blocks cross-origin reads — the on-screen code still shows it but the download falls back to the monogram, with a note saying so.

Rules that protect the printed result

  • Contrast is refused, not warned about. A foreground that is not darker than the background, or a pair under 3:1 contrast, disables the download.
  • Error correction is forced to the highest level (H) when a centre mark is present.
  • Check the margin. Printed codes need a clear quiet zone around them or scanners struggle. Export at a larger size than you think you need.

If a finished code will not scan, the usual causes are too little margin or scaling it down too far; export larger and keep the quiet zone clear.

Sub-accounts

An account can delegate to many teams, branches or sites. Each gets a sub-account with its own links and its own administrators, all under your account's name.

Each sub-account holds the same one-link-at-a-time budget as the account itself.

What is a sub-account?

A sub-account is a namespace under your account's own name, with its own links. Your account's short name is the parent; sub-accounts sit underneath it. A link called promo in a sub-account called northside inside an account called retail is reachable at go2.education/retail/northside/promo — and from the branded host form retail.go2.education/northside/promo.

What you get with a sub-account

  • A separate address space: the same link name can live in two sub-accounts without conflict, because names are unique within one space, not across the account.
  • Separate administrators: a person can be given a role that applies to one sub-account only (see Roles). A sub-account administrator can reach their own sub-accounts and nothing else — not other sub-accounts, not the parent, not billing.

One level deep, and no deeper

A sub-account hangs off the root account only. go2.education/retail/northside is the deepest namespace supported — a third level is not supported. The console will not let you create one.

Your visitors never sign in

Following any of these addresses is a plain redirect. Signing in applies to the management console, never to the links themselves.

Managing sub-accounts

You create, rename, comment on, disable, duplicate and delete sub-accounts from your own console.

Creating a sub-account

In Sub-accounts → New, enter a name. The name follows the same rules as link names: lowercase letters, numbers and hyphens (no underscores), up to 63 characters, no leading or trailing hyphen. It is checked against:

  • the DNS-label grammar (the name must work as a host label),
  • the platform's reserved names (app, admin, api, …) — refused,
  • additional reserved names protected by your operator — refused,
  • names already live on the account — refused.

If a sub-account cannot be created fully, it is removed automatically. Its address is shown as the path form (go2.education/yourname/<sub>).

Renaming

A sub-account can be renamed. The old address stops resolving (it answers not found), the new one starts, and the link inside keeps redirecting. As with links, a name already printed on materials dies when you rename: rename before you distribute, or keep the old one.

Comment, enable and disable

  • Comment — your own note about who or what the sub-account is for.
  • Disable — the sub-account's addresses stop redirecting (not found). Reversible, and distinct from deleting.

Duplicate

Copy a sub-account's settings (comment, enabled state) under a new name. The copy starts empty — links are not copied. If you need the same destination in the new space, create its link there.

Deleting

Only an empty sub-account can be deleted. One that still holds links answers subaccount_not_empty and names exactly how many links stand in the way. Delete the links first, or keep the sub-account.

Deleting frees the name.

Users and roles

An account is used by people. Each person signs in with their own address and has a role that decides what they can do.

The account owner manages people: only the owner can invite, change a member's role or remove a member. A sub-account administrator can manage the people working inside their own sub-accounts using the per-scope roles described in Roles.

Inviting users

The account owner invites people by email address. The invitee receives a link, opens it, sets a password, and a membership is created with the role the owner chose — the new person appears on the account immediately.

How the invitation works

  • The invite is a short-lived, single-use link. An already-used or expired link cannot be redeemed.
  • Invitations are delivered by email.
  • Only the owner invites, changes a role, or removes a member.

Choosing a password

The invitee's new password follows the same rules as signup: at least 12 characters, a symbol, not a common guess, and it must not contain their email's local part. See Creating an account for the full list of rules.

Per-scope roles

Someone with the right to manage a sub-account can give a member a role that applies to one sub-account only, overriding their account-wide role inside that sub-account. This is how a person works only in northside without ever being able to reach the parent account or other sub-accounts. See Roles.

Roles

Every account has six roles. There is no free-form permission editing.

RoleCan do
Account ownerEverything on the account, including billing, and the only role that can invite people, change a member's role, or remove a member.
Account administratorEverything except changing billing and managing people: account details, all sub-accounts and all links.
Billing administratorBilling (read and change), plus read-only access to the account, links and usage.
Sub-account administratorLinks and settings within their own sub-accounts only.
Link editorCreate and edit links; nothing else — no deletes, no sub-accounts, no people, no billing.
Reporting viewerRead-only access to links and usage.

Restrictions

  • Only the owner manages people. Inviting, re-rolling and removing members is part of being the owner. The last owner on an account cannot be removed, so an account never ends up with nobody able to manage it.
  • A sub-account administrator cannot reach the parent account, other sub-accounts, or billing.

Per-scope roles

A person's account-wide role can be overridden inside one sub-account: the person managing that sub-account can give a member a role that applies only there (sub-account administrator, link editor or reporting viewer). This is how someone works only in northside — their access inside every other sub-account, and the parent, is unaffected.

Settings

Settings holds your own details — your name, password, appearance, and time zone. Account details shared by the team are further down the same page.

Profile

  • Display name — shown next to your activity.
  • Email — shown here. Cannot be changed here.

Password

Appearance

  • Light, dark or system. System follows your computer's setting.
  • Time zone.
  • Show site icons.

Account details

The account name, company, and billing contact are shared. Changing them requires the account administrator role (see Roles).

Billing

See Billing.

Billing

New accounts are invite only. Contact us for a custom quote.

Single sign-on (SAML / OIDC)

Single sign-on is coming soon. It will be optional.