Accounts & signing in
Pingloop has no guest mode. Every screen in the app requires a signed-in account, and every API call carries that account's token.
How a session works
- You open any app URL. Without a session the browser is sent to the sign-in page, remembering where you were headed.
- You sign in with your workspace email and password. The API returns a signed token valid for 7 days.
- The app verifies the token before rendering, then takes you to the page you originally asked for.
- If the token expires or is rejected, the session is cleared and you return to sign-in with a note explaining why.
Signing out clears the session everywhere it is held. There is no "remember this device" beyond the 7-day token.
Your role decides what you see
The role you hold in the active workspace drives both halves of access control:
- The sidebar hides modules your role cannot view.
- The API rejects calls your role cannot make, so a hidden link is never the only protection.
| Role | Typically sees |
|---|---|
| Owner | Everything, including billing and workspace ownership |
| Admin | Everything except workspace ownership |
| Manager | Queues, SLA, reports, tickets and the inbox |
| Agent | Inbox and tickets |
| Viewer | Read-only access to what it is granted |
Owners always have full access. Everything else is configured under Settings → Roles & Permissions.
Multiple workspaces
If your account belongs to more than one workspace, the switcher in the top bar lists them. Switching changes the active workspace for every subsequent request; your session stays the same.
Creating a workspace
Create one on the sign-in page registers an account and a workspace together and makes you its Owner. You can invite your team immediately under Settings → Team & Staff.
Getting an account
Accounts are created by an Owner or Admin under Settings → Team & Staff, who set your role at the same time. If you cannot sign in, ask them to confirm your account exists and which workspace it belongs to.