Admin console
The admin console is a set of web pages your gateway serves at https://<your gateway>/console/. Portward doesn’t
host it. Admins sign in with their work account at your directory; anyone else is refused. It works when the gateway
signs people in through your company directory, which is how the AWS, Azure and Google Cloud templates set it up.
With WorkOS sign-in there is no console, and you use the admin connector instead.
The console and the admin connector change the same settings. Use whichever suits the task: the console for lists and reviews, the admin connector for connecting sources, writing context and settling definitions in plain words. A few things are only in one of them:
| Only in the console | Only in the admin connector |
|---|---|
| Limit datasets to groups, and preview what groups get | Write and save context |
| Show more of a column to some groups | Settle definitions and confirm links |
| Admin and user groups, database hosts, expiry reminders | What the AI may change on its own |
| Who has signed in | |
| Export answer records |
The console signs you out after 30 minutes without a request, and after 8 hours in any case. Theme switches light and dark, and Sign out is at the top.
Overview
Section titled “Overview”Is the gateway healthy, and what needs you now.
- The banner reads Gateway healthy, Gateway running, 2 items need attention, Something is down or Logs need attention, with the version and how many sources are live.
- Needs attention lists source errors, logs that don’t verify, a certificate or noted secret within 30 days of expiry, a fresh sign-in that is turned off, and a data connector open to everyone the directory signs in. Each item links to the page that fixes it. On a new gateway it starts with Connect a source.
- Sources, Certificate (days left on the gateway’s TLS certificate), Expiring secrets, Last 7 days (answers, people, reveals, each linked to its list) and License (the license and the seats in use).
Sources
Section titled “Sources”Each source with its kind, number of datasets and status. Connect a source opens a form per kind. Passwords and keys go straight to the gateway, encrypted, and are never shown again. After you connect, the console opens Datasets, because a new source exposes nothing yet. Each row has:
- Re-check: connect again and refresh the status and table list.
- Reconnect: change the settings or the password of a source added by an admin. Your rules are kept.
- Disconnect: forget a source added by an admin (Dataset access).
Sources from the config file have only Re-check; you change them in the config file. Connect a source has what each kind needs.
Datasets
Section titled “Datasets”Pick a Source. Each table has the Exposed to the AI and to people switch and one row per column: AI sees, People see, Send to AI and Token type, with By group for tokenized columns. A legend says what leaves the gateway for each setting. Save saves every change on the page; Discard drops them. What people and the AI see explains each setting.
Access
Section titled “Access”- Admins and Data users: the groups, from the config file and added by an admin, with Add.
- Datasets by group: who may use each dataset, with Change.
- Preview: what someone in given groups gets, column by column.
- People: who signed in recently, their role and groups.
See People and groups and Dataset access.
Records
Section titled “Records”Three tabs: Answers (search, filters, evidence packs and Export matching (JSON)), Changes (the setup log) and Reveals and shares. See Audit and evidence.
Settings
Section titled “Settings”- Database hosts setup may connect to (Approvals and safety).
- Expiring secrets to be reminded of (Approvals and safety).
- Sign-in, read only: the directory, app ID, where groups come from, whether a fresh sign-in is asked for more access, and the callback address. These are set in the config file.
- Gateway, read only: the address, version, Rows per answer, Smallest group for totals and the source kinds allowed.