The Enterprise console is where a team is run: who is in it, which licences they hold, how much the team is getting out of Sprecho, and which policies apply to their devices.
It lives at enterprise.sprecho.ai. Sign in with the account that owns or administers the team. If you land on a page saying Enterprise is required, the team is not on that plan yet; if it says only the owner can access the console, you hold the member role.
admin.sprecho.aiis a different application — Sprecho's own internal operations portal. The console for your organisation isenterprise.sprecho.ai.
What the dashboard shows
The landing page answers "is this worth what we pay for it?" with five figures for the selected period:
| Card | What it means |
|---|---|
| Time saved | Total time saved by dictating instead of typing, with the change against the previous period |
| Money saved | The same figure priced at an hourly rate. The rate is yours, entered locally, and is never stored on the server |
| Dictations | How many dictations the team produced, with a per-member breakdown |
| Active members | How many people dictated in the last seven days, out of the total |
| Licence cost | What the current seats cost per month, and how many times over the time saved has paid for it |
Below that:
- A member table with each person's numbers and a CSV export.
- Apps in the team — which applications people dictate into most, which is usually the fastest way to see where Sprecho actually landed in the workflow.
- Time of day and saved per day charts.
Figures are grouped in the team's configured time zone, so a report matches the working day people recognise rather than UTC.
What administrators cannot see
Nothing in the console exposes dictation content. Owners and admins see counts, durations and application names — never the text of a transcript, never the audio. That boundary is enforced on the server: an administrator requesting another member's transcripts is refused, not merely offered no button.
If your works council or data protection officer asks what management can read, that is the answer, and it is the same for every role.
The rest of the console
| Section | What you do there |
|---|---|
| Members | Invite, remove, and change roles between admin and member |
| Licenses | Buy seats, assign and unassign them, manage the subscription, billing address and invoice history |
| Dictionary | Maintain the team's shared vocabulary |
| Snippets | Maintain shared text blocks |
| SSO | Connect your identity provider, verify domains, issue SCIM tokens, map groups to roles |
| Device Management | Set the device policy, review enrolled devices, read and export the audit log |
| Downloads | Get the signed installers for managed deployment |
| Settings | Account, general preferences, dictation languages |
Policies you set here
- Retention — how long transcripts and audio are kept for every member. Set by the owner, enforced on the server, and it overrides individual settings while someone is in the team. There is also a "delete all team conversations" action, which is immediate and irreversible.
- Device policy — locks, allowed languages, allowed hours, update control and what device data is collected. See manage enrolled devices.
- Single sign-on — including whether SSO is enforced for your verified domains.
Retention is worth setting deliberately rather than leaving at the defaults; see turn off transcript and audio storage for what each option really does.