FAQ
Questions we keep getting. If yours isn't here, drop us a line.
Those are public-link shorteners — you make yourdomain.com/abc123 and put it on a poster. slashgo is team-scoped go/ navigation for internal docs. Different job.
Yes. The recommended path is the Chrome extension: it intercepts http(s)://go/<slug> locally and redirects to slashgo.io — no DNS to configure. It also adds a Google-search fallback (it catches the search and redirects) and the `go <slug>` omnibox keyword. For non-Chrome browsers, point `go` at us with one DNS record (go CNAME go.slashgo.io) and the server does the redirect instead — see the setup guide.
It's the recommended path — smoothest by far, and zero IT. You don't strictly need it: the DNS fallback (go CNAME go.slashgo.io) makes go/ resolve in any browser server-side. The one rough edge there is that a dotless `go` can't have a TLS cert, so HTTPS-first browsers can stumble — which is exactly what the extension avoids.
The 11th person joins normally. Owners and admins see a banner asking them to upgrade to Pro for $5/mo. We never fail an invite to force an upgrade.
Current click counts (total / today / week / month) and trending links are on every tier, including Free. Date-range history charts, 12-month trends, and top-links breakdowns are part of Pro.
At rest, yes — AES-256, on every plan, with no way to turn it off. Plaintext is only decrypted in memory at redirect time, never written to disk. (Note: we hold the key — this is encryption at rest, not end-to-end.)
On Team, yes. Everyone can search by name, description, and tags. Searching by the destination URL is a Team feature because URLs are encrypted at rest — that search decrypts your org's links in memory at query time (never to disk), so it's heavier and we gate it.
The extension is Chrome/Edge (Chromium) for now; a Firefox build is on the roadmap and reuses the same rules.json. In the meantime every browser is covered by the DNS fallback (go CNAME go.slashgo.io) — the server does the redirect, no extension required.
It's a Team feature an owner enables in Settings → Organization → Workspace governance. Two things are needed: (1) a Workspace super-admin email we delegate read-only directory lookups as, entered in that panel; and (2) a one-time authorization in your Google Admin Console under Security → Access and data control → API controls → Domain-wide delegation — add SlashGo's service-account Client ID (shown in the setup panel) with the single scope https://www.googleapis.com/auth/admin.directory.user.readonly. Once both are in place, flip the toggle. We only ever read user status (suspended/deleted) — never write to your directory, and no SAML. When someone is suspended or removed in Workspace, SlashGo deactivates them here within the hour and reassigns their links to an owner.
Yes. SlashGo exposes signed read-only resolution through Cmdline's MCP bridge. Approved agents can resolve go/ slugs without a user login.
Email us. Team customers get priority support.