Administrator Overview
This page is for Owners and Admins of an SKH organisation and gives an overview of every administrative area. Each area has its own detail page.
Which role does what?
SKH ships three built-in roles per organisation:
| Role | Description |
|---|---|
| OWNER | Highest level. Can do everything, including billing and owner transfer. |
| ADMIN | Manages members, workspaces, integrations, MCP servers and LLM configuration. No access to owner-only actions. |
| MEMBER | Standard user. Sees and edits whatever is allowed via workspace/page memberships and permissions. |
In addition there are custom roles with fine-grained permissions over the actions Create / Read / Update / Delete and the resources Workspace / Page / Folder / File / Member. Details: Members, Roles & Groups.
The Settings sidebar
The gear icon or Settings entry in the main navigation opens the tenant settings, organised into four groups:
Organization Management
- Organization – Name, description and URL of your organisation.
- Members – Invite, change roles, remove members.
- Roles – Create custom roles and assign permissions.
- Groups – Groups for bulk-assigning workspace and tool access.
- Theme Configuration – Branding, logo, light/dark theme colours.
User & Access Control
- User Workspace Management – Manage members × workspaces as a matrix.
AI & Data
- LLM Scope – Which research modes (Internal, Web, MCP, Hybrid, Deep Research) are allowed.
- MCP Servers – Register tools and grant permissions.
- Model Profiles – Personal BYOK profiles (each user manages their own).
- Model Policy – Which BYOK providers are allowed organisation-wide, plus the BYOK audit log.
Integrations
- Integrations – Connect OneDrive, Google Drive, SharePoint and (when enabled) Dalux/Zipro.
This handbook's detail pages:
| Area | Detail page |
|---|---|
| Members, Roles & Groups | members-roles |
| Integrations | integrations |
| MCP Servers | mcp-servers |
| LLM Scope, Model Policy, BYOK | llm-configuration |
| Branding & Theming | branding |
| Billing & Subscription | billing-subscription |
First tasks for a new organisation
- Set organisation data – Name, description, URL under Settings → Organization.
- Configure the theme – Upload logo, tweak colours under Settings → Theme Configuration.
- Choose LLM scope – Default is "internal only". To use web search, MCP or Deep Research extend the scope here.
- Invite members – By e-mail or via CSV bulk import under Settings → Members.
- Refine roles – If the built-in roles aren't enough, define custom roles under Settings → Roles.
- Build workspaces – Under My Hub in the main navigation. Structure by department or project, with the right member/role assignments.
- Connect integrations – Enable OneDrive/GDrive/SharePoint if you want content mirrored from those sources.
- Register MCP servers – Optional. If your team should call tools like Jira, GitHub or your own APIs from chat.
Dashboard
The Dashboard in the main navigation shows:
- A header card with workspace count, organisation count, your role and subscription status.
- Secondary metrics: team size, number of chats, member since.
- Charts: workspaces per organisation, activity overview.
- A warning if there's no active subscription – with a direct link to billing.
Detailed usage and storage metrics live under Billing → Usage.
Compliance features
SKH automatically logs security-relevant actions and surfaces them to owners:
- BYOK audit – Under Settings → Model Policy → Audit tab you see every switch from an SKH Standard model to a BYOK model in the last 30 days, including user, time, provider and chat reference.
- File and page activity – On file and page detail pages the most recent activity (who changed what, when) is shown inline.
Data protection notes
- FADP/GDPR – Used exclusively with the SKH Standard models (DeepSeek V3, Kimi K2.5, Mistral Medium 2505), processing stays inside Switzerland and the EU.
- Encryption of sensitive fields – E-mail addresses, names, message content and API keys are encrypted at rest in the database.
- BYOK awareness – If you enable BYOK, you're responsible for making sure your team understands the data-flow implications. A warning modal on first switch and an amber strip while a BYOK model is active are built into the UI.
When to escalate to platform support
- Subscription issues that aren't solvable via Stripe self-service.
- Suspected data-protection breaches or unauthorised access.
- Custom domains, SSO setups, individual plan agreements.
- Requests for vertical integrations not enabled by default (Dalux, Zipro).
Contact: via the support entry in the sidebar help or the official platform e-mail.