Skip to main content

Run GOAT

Operators and sign-in

Who can sign in to build, and how.

Operators are the people who sign in to GOAT itself: the admins who run it and the authors who build dashboards in it. The people who use embedded dashboards in your product never sign in to GOAT; see Viewer tokens.

Roles​

RoleWhat they can do
AdminEverything an author can do. Also manages operators in Identity, creates and revokes API keys, and changes install-wide settings.
AuthorBuild datasets, collections, charts, and dashboards, and publish them. Read the list of API keys.
Viewer (operator)Set only by the install's sign-in settings, never in the app. This kind of operator can open the app's screens but cannot save changes. It is not the same as the people who use embedded dashboards.

A person who signs in with no role set is treated as an author.

How people sign in​

The sign-in page offers the ways your install has set up:

  • Continue with Google, for people in your company's Google Workspace domains.
  • Sign in with a password, for the install's first admin account.

A Google account is let in only if it belongs to one of the install's Workspace domains. A personal account that uses a work address is not.

Within those domains, who gets in depends on the install's sign-in settings, which are chosen when GOAT is installed. The install can let in only the people on the Identity list. This page is written for that setting. It can instead let in everyone in its domains as an author or a viewer. Then no one sees "No access to this install", and the Identity list sets roles rather than deciding who gets in. The install's sign-in settings can also name people and their roles directly.

For an account with a second factor, GOAT asks for the code from an authenticator app after the password.

The first admin​

The install's first admin account is created when GOAT is installed. It signs in with a password and a second factor, with one authenticator set up for each person who holds it. It is the install's break-glass account, so no one can lower its role or disable it in the app. Keep its password and authenticator keys where the people who run the install can reach them.

Add operators​

An admin opens the account menu, chooses Admin, then the Identity tab, which lists everyone who can sign in.

  1. Choose Add user.
  2. Under Addresses, enter one or more Google addresses. Use each person's main Workspace address, not an alias.
  3. Choose a Role, then Add.

Each person is let in at their first Google sign-in, with that role. Adding people needs Google sign-in set up for the install.

Access requests​

A person who signs in with Google but is not on the list sees "No access to this install", and can request access. An admin sees the request in Identity, marked Pending, and in Notifications under Access requests.

  • To approve, select the person and choose Set role.
  • To refuse, choose Decline. They cannot sign in or ask again until an admin sets a role on their declined row.

A request no one answers lapses after 30 days.

Change or remove access​

In Identity, select one or more people, then:

ActionWhat it does
Set roleChanges their role. It reaches someone already signed in within the hour.
DisableStops them signing in. Sessions already open end within the hour. Re-enable undoes it.
RemoveTakes someone off the list before they ever sign in. For someone who has signed in, use Disable.

You cannot lower your own role, or disable yourself; another admin can. A role marked "Set by your identity provider" comes from the install's own sign-in settings, not from Google Workspace. Whoever runs the install changes it there.

What the Identity list shows​

StatusMeans
ActiveCan sign in.
PendingAsked for access; waiting for an admin.
Not signed in yetAdded, and has not signed in.
DisabledCannot sign in until re-enabled.
DeclinedAsked and was refused.
No longer admittedHad access, but the install's sign-in settings no longer let them in.
Password, from before SSOA password account from before Google sign-in was set up.
No accountOn the list, but no sign-in account exists for them.

How long a sign-in lasts​

A sign-in lasts at most 12 hours. Fifteen minutes before the end, GOAT shows a notice ("Your session will refresh in 15 minutes."). At the limit it asks you to sign in again, and the page you were on stays as it was.

Common problems​

What you seeWhat to check
"No access to this install"The person's address is not on the Identity list. They can request access, or an admin adds them.
"This account signs in with your organization's account, not a password."Use Continue with Google.
"This way of signing in is not set up for this install; ask an admin."The install has no such sign-in. Ask whoever installed GOAT.
Add user says Google sign-in is not set upThe install needs Google sign-in before people can be added. Ask whoever installed GOAT.
A new role does not show yetIt reaches a signed-in person within the hour. Signing out and in again applies it at once.
GOAT documentation

Type to search.