“He left on Friday. Did his AI leave too?”
Access follows the directory and the revocation
Platform · Security and deployment
Who gets in, what they can do, and what gets recorded.
Each person signs in with their own account and uses only the functions their role allows. A sensitive action waits for a person, and actions are recorded.
See how it worksSkyller · Activity trail
Activity trail
Documents| Time | Person | Action |
|---|---|---|
| 09:42 | Carla | Document published |
Demonstration · illustrative data
FOUR ACCESS PROFILES
reviewing and approving documents are separate duties
FUNCTION BY FUNCTION
each team gets only what the work needs
SENSITIVE ACTIONS WAIT
high or critical risk waits for a person
ACTIONS ARE RECORDED
author, action and resource in Activity
Where this shows up in your day
The questions nobody can answer about the company's AI.
They surface after a scare. In Skyller, each one has an answer you can show on screen.
“Can the AI delete this on its own?”
A sensitive action waits for a person
“Who saw it, who changed it, who approved it?”
Trail filterable by person and resource
How it works
From sign-in to action, five controls in sequence.
No one needs to understand security: people work and ask; the company decides up front how far each request can go.
01
Identity
Each person signs in with their own account: the company network sign-in (Active Directory), corporate single sign-on, Google, Microsoft or a Skyller account with two-step verification. No shared accounts and no master key.
02
Role
Four profiles define what each person can do on the platform. Reviewing and approving documents are assigned separately: being an administrator does not grant the power to approve.
03
Function by function
The company connects a system once and enables only the functions needed, per person or group. The same request runs for one person and only looks things up for another.
04
Approval by risk
High- and critical-risk functions stop and wait for a person to decide: in the chat, in the approvals inbox or in the team's channel. Each approval is valid only for that action.
05
Record
Actions are recorded in the activity trail, with who did them and when, by resource type: connections, approvals, documents, members and sign-in.
Skyller · Access to the Customer Service workspace
Access to the Customer Service workspace
Customer Service group| Resource action | Permission |
|---|---|
| View documents | Allowed |
| Edit content | Allowed |
Demonstration · illustrative data
Live proof
The same sentence, two people, two outcomes.
Permission applies to the person who asked, not just to the agent.
Two people ask
“Reply to Aurora about the September collection and send the email.” Ana, from Finance, and Bruno, from Purchasing, send the same sentence to the same agent.
What happens
- 01Skyller identifies the function in the connected system and checks whether the person asking may use it.
- 02Ana has the function enabled, and the company required confirmation for emails to customers: Skyller drafts the email, opens the approval card and waits.
- 03Bruno's role does not include the function: Skyller looks up the history and drafts the text, but does not send the email and says so in the conversation.
Result
Two decisions from the same sentence, both in the trail: who asked, what was enabled, who approved and when.
Good to know
- Function-level permissions apply to connected systems that expose each function separately; with the others, Skyller looks things up and drafts the text.
- Approving from Slack or Telegram requires the channel connection to be purchased and configured; without it, the decision happens in the chat or the approvals inbox.
Where each thing happens
SaaS operated by Skyller as the default. Your own infrastructure as a project.
What stays with Skyller, what stays with the company and what remains external in both: channels, web search and, unless a project replaces them, AI models via API.
Deployment modes
Default for every plan
SaaS hosted and operated by Skyller
Application, database, document index and files run on infrastructure operated by Skyller, with one organization per company and isolation enforced by the database itself.
Processing, providers and deletion follow the DPA and the Trust Center.
Enterprise · per project and contract
Customer-controlled infrastructure
In the customer's own cloud or local environment, with deployment led by Skyller. It is an Enterprise proposal, sized with the company's IT team.
What runs inside the environment is defined in the project, component by component.
Fully local operation, with AI models, storage and connections inside the customer's environment, applies only when each piece is local and stated in the project and the contract.
Location and processing board
Component by component, in both modes.
| Component | SaaS operated by Skyller | Enterprise on customer infrastructure |
|---|---|---|
| Application and database | SaaS operated by SkyllerSkyller's infrastructure, one organization per company, with isolation enforced by the database itself. | Enterprise on customer infrastructureIn the customer's own cloud or local environment. |
| Documents and search index | SaaS operated by SkyllerSeparated per company on Skyller's infrastructure; earlier versions are preserved. | Enterprise on customer infrastructureIn the project's environment, with the same per-company isolation. |
| AI answers from external models | SaaS operated by SkyllerPrompts, context and files go to the providers listed under integrated services, never used for training, including on the fallback route. | Enterprise on customer infrastructureThe same providers via API, unless the project swaps them for proven local models. |
| Models running on Skyller's servers | SaaS operated by SkyllerReading documents and scanned pages, transcribing audio, reranking searches, memory and tool selection. In a fallback, they may use providers from the list. | Enterprise on customer infrastructureRequire GPUs in the customer's environment, sized in the project. |
| Connected systems (ERP, CRM, in-house system) | SaaS operated by SkyllerThey stay where they are. Skyller calls only the enabled functions, with the credential authorized for that person. | Enterprise on customer infrastructureSame; the bridge to internal systems can sit inside the customer's network. |
| Channels (Slack, Telegram, WhatsApp) | SaaS operated by SkyllerAn add-on connection; messages pass through the channel provider's infrastructure. | Enterprise on customer infrastructureSame; the channel remains external. |
| Web search by the tools | SaaS operated by SkyllerExternal services from the integrated-services list, used only when the tool is triggered. | Enterprise on customer infrastructureSame; they remain external. |
| Sign-in and identity | SaaS operated by SkyllerIdentity provider operated by Skyller; the company directory still controls the password. | Enterprise on customer infrastructureDefined in the project; the customer's directory remains the source. |
Server requirements are sized per project: GPUs, memory, storage, concurrent users and document volume. There is no single number and no off-the-shelf fully local plan.
Real application
An offboarding, from the directory to the trail.
- 01HR
Deactivates the person in Active Directory at 5 p.m., as with any other system.
- 02Skyller
The person can no longer sign in with the network login; the session that was open expires within hours.
- 03Administrator
To cut it sooner, revokes access in Members: Skyller ends the sessions, removes the seat and revokes API keys, personal credentials and personal connectors.
- 04Skyller
Records each decision in the trail: who revoked what and when.
- 05Audit
Months later, filters the trail by the person and rebuilds the sequence without relying on anyone's memory.
For your IT team
What IT will ask, with the answer and the limit.
Select a topic to see its capabilities, conditions, and limits.
- Company single sign-on
- SAML or OIDC, with a domain verified in DNS; together with Active Directory, it makes up company sign-in. A seat report flags who is missing, who is left over and mismatched roles. Company sign-in is available on Corporate, Enterprise.
- The company's Active Directory
- Read-only federation with the directory: Skyller does not edit or delete federated users, syncs the profile periodically, and the directory controls the password.
- Two steps and password attempts
- Authenticator app, turned on by the person or required by the administrator. Repeated wrong-password attempts lock the account for a while.
- Sessions and sign-in history
- Each person sees where the account is signed in and ends any session they don't recognize. Sign-in history, including wrong passwords, comes from the identity provider.
- Encrypted, revocable credentials
- Credentials for connected systems are encrypted in the database; a personal one can be read only by its owner, not even the administrator. On offboarding, they are revoked along with the access.
- Isolation between companies
- Each company is a separate organization in the identity provider. The database itself enforces isolation, including for the table owner; index and files are separated too.
- Models, data and deletion
- Third-party models via API, from the public list of integrated services, with no use of company data for training. Chat attachments expire in 24 hours; document versions are preserved; deletion follows the DPA.
- Activity trail
- Actor, action and resource, filterable by action, resource and person in Settings › Activity; source address and browser appear on some events. Changes to what tools an agent can reach record the before and after.
- Risk per function
- Safe, Medium risk, High risk or Critical: high risk and critical stop by default, and the company can require confirmation at other levels and lock the rule; without the lock, the person may skip it. Each approval carries a signature tied to the action and the company.
Questions from whoever decides
What usually holds the security assessment back.
Next step
Bring your company's security questionnaire.
See profiles, approval and the trail working in the free trial, or book a demo and bring your IT team's questions.