Agency

Client sign-in

Let each client sign in to their own dashboard, showing only their websites and only the pages you pick, under your brand.

1. Set a sign-in name

In Branding & domain, save your brand and a Sign-in name, such as meridian. It makes your sign-in page:

https://seentics.com/signin?agency=meridian

That page shows your brand name, logo and colour. With Hide Seentics branding on, it shows no Seentics marks.

2. Invite a client user

Open the client from Clients in the Agency workspace.
In Client sign-in, choose Invite, enter their email and, if you like, their name.
They get an email in your brand with a sign-in link. The link works once and lasts 15 minutes.

The user shows as Invited until they first sign in, then Active. The panel also shows your sign-in link, ready to copy.

3. Share the sign-in link

Give clients your sign-in link to bookmark. They enter their email and get a new link each time. No passwords. The page never says whether an email belongs to a client user, so it cannot be used to check who your clients are.

Link expired?

A used or expired link shows a page to ask for a new one. You can also choose Resend link next to the user.

What clients see

Only their websites: the websites under their client, nothing else in your account.
Only the pages you choose: pages set to View or Edit in the client's Features table. Pages set to Off are hidden from the sidebar and closed if opened by address.
Settings: Goals and Privacy only, when you allow them. Never billing, team, developers, tracking code or deleting a site.
Your brand: name, logo and colour on the dashboard. With Hide Seentics branding on, no Seentics links, chat or logo.

View or Edit

Setting	What the client can do
Off	The page is hidden.
View	Reads the page. Buttons that create, change or delete are hidden or disabled.
Edit	Reads the page and can create, change and delete there, such as funnels, goals or lead status.

The server enforces these, not just the dashboard: a request for a page that is off, or a change on a page set to View, is refused with 403 feature_not_allowed. Changes in the Features table apply on the client's next page load.

Revoking access

Action	Effect
Disable	Keeps the user but blocks sign-in and ends their sessions.
Enable	Lets a disabled user sign in again.
Remove	Deletes their access to this client.
Resend link	Emails a fresh sign-in link.

To share a dashboard without a sign-in, use an embed link instead.

With the API

The same actions are in the Agency API:

GET /agency/clients/:id/users and POST /agency/clients/:id/users ({ email, name? }, sends the invite)
PATCH /agency/clients/:id/users/:userId (status, name) and DELETE /agency/clients/:id/users/:userId
POST /agency/clients/:id/users/:userId/send-link