structuraldata model
No path between tenants
Three tenants, three datasets, three identities. A request from one carries no credential that the others would honor. The column that scopes every row is not a filter a teammate can remove.
tenant A
AUDIT TRAIL · live
tenant · #8217Every line attributable
Last 5 minutes · ticket #4471 · six actors on the record
- customer · Maria B.12:04:11WhatsApp inbound · read
- assistant · warehouse-ops12:04:14read thread summary · scope: ticket #4471
- agent · anarezende12:11:32Slack message · scope: #logistics-ops
- assistant · tool call12:18:02store.orders.refund · approved by m.bennett
- connector · payments12:18:30charge #ch_8830 · tenant scope only
- system · sms12:19:00outbound · receipt logged
Nothing happens off-record.T+0:14
A live audit feed. Customer, agent, assistant, connector, system: all on the same record.
A security field guide
Security is a set of controls
enforced where the work happens.
Real engineering, scoped to one tenant, signed by one identity, read by one audit trail. The controls live in the data layer, the identity model, and the tool call, not in a separate security tab.
At a 40-person consumer brand, every assistant tool call in the first 90 days carried an identity, a scope, and a reversible permission. (Composite illustration.)
Tenant isolation
Your data lives inside one boundary.
Crossing it is structurally impossible.
The tenant is the security boundary. Every query, every assistant action, every file lookup carries a tenant scope. There is no API path, no admin command, no assistant tool call that crosses from one tenant to another. The isolation lives in the data model, not in a policy a teammate could relax.
Where the boundary holds
- Query layer
- Assistant tools
- File storage
- Identity scope
- Audit trail
Identity
Your identity provider runs the door.
Or ours does, and yours plugs in.
IDENTITY SERVERbootdesk.id
shippedOne identity model for everyone who touches a ticket: your staff, the assistant, the automations, the connectors that reach out on their behalf.
mode A
BootDesk as IdP
Accounts live here. Sign in to BootDesk, sign in to everything.
mode B
Accept yours
Wire your corporate identity. Single sign-on in, sessions out.
mode C
Both at once
Internal staff on yours, contractors on ours, one workspace.
Who authenticates
- Staff users
- Assistants
- Automations
- Connector invocations
One door. Many keys. Same audit.
Attribution · audit trail
Every action leaves a name.
Every name is on the record.
Every assistant call, every staff message, every connector invocation runs under a scoped identity. Every grant, every file access, every tool call touches the same audit trail. When something goes wrong, you know who or what did it. Compliance teams can read it. Nothing happens off-record.
Audit export · tenant #8217 · 24h window
illustrativeJSON · CSV
timeactoractionscoperesult
09:14:02agent · m.bennettopened ticket · assigned to selfticket #4488ok
09:14:30assistant · summaryread last 14 days · drafted replyticket #4488ok
09:15:11assistant · tool callstore.orders.refund · amount $42.00ticket #4488
File security
Every file gets scanned at the door.
Every signature stays inside.
Scan at intake. Sign in place. Expire on close.
Every file that enters a ticket is scanned before it can be opened. Documents edit inside the platform, nothing leaves to get a signature. Shares sign and expire. The file never travels somewhere unprotected to collect a mark.
Inbound · ticket #4471
3 filesrouting-slip-8830.docx
uploaded by customer · 248 kb
invoice-8830.pdf
uploaded by customer · 92 kb
payload.exe
The assistant works under your permissions.
Nothing more, and you can revoke them.
The assistant operates under permissions your admins granted. It cannot exceed them. Every tool call is logged beside the ticket. You can revoke any permission at any time, and the assistant stops reaching for that tool on the next request.
Assistant · warehouse-ops
4 grants · 1 revoked- active
store.orders.read
Read order status, history, tracking.
- active · 24h
store.orders.refund
Issue refunds up to $50. Above requires agent approval.
- active
sms.outbound
Send transactional notifications to ticket contacts.
- active
slack.post · #logistics-ops
Post updates to one channel. No DM access.
- revoked
payments.dispute
Revoked 09:42 after policy review.
Grants are scoped to an assistant, a tenant, and a tool. No wildcard grants. No grant outlives the admin who issued it unless another admin renews it.
Enterprise tier
Single sign-on, audit exports, retention.
The controls enterprise buyers expect.
The controls below ship at the Enterprise tier. They layer on top of the tenant boundary, the identity model, and the audit trail you already have. Nothing here is a substitute for the foundations. It is the set of levers a security or compliance team expects to pull.
Enterpriseshipped
OIDC
Full single sign-on as provider or consumer. Connect your corporate identity system to BootDesk, or let BootDesk issue identities to the apps around it. Group claims, scopes, and session lifetimes map cleanly.
Works with any standards-compliant identity provider your security team already operates.
sign-on · session · scopes
provider or consumer
Enterpriseshipped
Advanced audit
Tamper-evident export to your SIEM. Streaming webhooks for real-time review.
Start free, or book a walkthrough.
We will show you the controls.
The free tier ships with the tenant boundary, the identity server, and the full audit trail. No trial timer. The walkthrough is thirty minutes with an engineer who can answer the questions your security team will ask.