Dashboard tour
The console is where the control plane is actually operated. Nine screens, each answering one question. What a given person sees depends on their role, so a Viewer and an Admin open the same URL and get different navigation.
Signing in
- Go to apps.msharti.dev and sign in. If you were invited, use the one-click link from your invitation email; it expires after seven days.
- You land in your tenant. Everything you see belongs to it and nothing crosses between tenants.
- Navigation reflects your role. If a section named below is missing for you, your role does not include it. See what each role sees.
Home
The state of the tenant at a glance: calls made against your quota, which connectors are live, which need attention, and recent activity. It is the screen to open when someone says "is it working?", because a connector with an expiring token shows up here before it shows up as a failed answer in an assistant.
Connectors
Where systems are connected, tested and disconnected. Each connector shows its status, the number of tools it exposes, and the health of its credential.
| Action | What happens |
|---|---|
| Connect (OAuth) | Generates a one-time Connect Link for your tenant. You approve on the provider's own consent screen. Tokens are stored encrypted and auto-refreshed. |
| Connect (credentials) | You paste values from the provider's console. Msharti tests the connection before saving so a bad credential fails here rather than mid-conversation. |
| Test | Runs a live call against the system. Use it when an assistant starts failing and you need to know whether the problem is upstream. |
| Disconnect | Removes the credential. Tools from that connector immediately disappear from discovery for every assistant in the tenant. |
Expiring soon. Connectors flag an approaching credential expiry ahead of time and send an email reminder. Renewing is one click and re-authenticates without downtime.
Usage
Calls over time, broken down by connector, tool and person. Three things it is good for:
- Confirming a call actually happened. The fastest way to tell whether an assistant read your data or improvised.
- Seeing what is actually used. Connectors nobody calls are candidates for disconnecting, which shrinks your exposure for free.
- Watching the quota. Daily limits are per tenant and shared across every agent and person. See limits and plans.
Data Retention
Msharti is a pass-through by default: business records are fetched, used to answer, and not kept. Retention is an opt-in add-on, configured per connector, for cases where you need a historical window that the source system does not give you, such as M-Pesa data beyond its own window. Nothing is retained until you turn it on here.
Team Admin only
Seats, invitations and the role attached to each person. Pending invitations count against your seat limit as well as accepted members. Full detail in teams and seats.
Roles & Access Admin only
Where policy is written. Create custom roles, choose the exact tools each may invoke from the live catalogue, and control which console sections the non-admin roles can see. This is the screen that turns "we should be careful with AI" into something enforced. See roles and permissions.
Billing
Plan, quota and invoices. Visible to Admin and Finance. Changing plan changes your connector allowance, daily call quota and seat count together; the current numbers per tier are in limits and plans.
Settings Admin only
Tenant configuration and API keys. Key management is the part that matters operationally:
- New key. Choose the assistant it is for and the role it carries. The role is what scopes it.
- Copy it once. Only the prefix is stored afterwards, so a lost key is replaced rather than recovered.
- Revoke. Immediate. Anything using that key stops on its next request, which is why one key per integration is worth the small extra effort.
Gateway Monitor Admin only
The live view of the gateway: requests arriving, tools being invoked, denials, and connector health. Where Usage answers "what did we do this month", the monitor answers "what is happening right now", which is the one you want open during a rollout or an incident.
Who sees what
| Section | Admin | Finance | Manager | Viewer |
|---|---|---|---|---|
| Home | ✓ | ✓ | ✓ | ✓ |
| Connectors | ✓ | ✓ | ✓ | ✓ |
| Usage | ✓ | ✓ | ✓ | ✓ |
| Data Retention | ✓ | ✓ | ✓ | — |
| Billing | ✓ | ✓ | — | — |
| Team | ✓ | — | — | — |
| Roles & Access | ✓ | — | — | — |
| Settings | ✓ | — | — | — |
| Gateway Monitor | ✓ | — | — | — |
Admins can adjust the non-admin rows under Roles & Access. The Admin column is fixed.