Set up the first administrator account
After a successful deployment, the Self-Hosted Controller displays the platform access credentials directly in the terminal. This guide walks you through retrieving those credentials, logging in, creating your first community, and allocating your subscription.
Before you begin
- You completed the post-deployment validation steps in Deploy the platform.
- You have the platform URL configured in
global.host(e.g.,https://app.sekoia.local). - You have the license file provided by Sekoia for your subscription.
Retrieve the initial credentials
At the end of a successful installation, the SHC displays a credentials table in the terminal output.
Example credentials table
Platform Access Credentials
┏━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Service ┃ URL ┃ User ┃ Password / Token ┃
┡━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ argocd │ http://localhost:8080 │ admin │ │
├──────────┼───────────────────────────────┼─────────────────────────┼──────────────────────────────────┤
│ grafana │ http://localhost:3000 │ admin │ │
├──────────┼───────────────────────────────┼─────────────────────────┼──────────────────────────────────┤
│ sekoiaio │ https://app.sekoia.local/user │ instanceadmin@sekoia.io │ │
└──────────┴───────────────────────────────┴─────────────────────────┴──────────────────────────────────┘
The table provides credentials for three services: the Sekoia platform (sekoiaio), the ArgoCD GitOps console (argocd), and the Grafana observability dashboard (grafana). Save all three sets of credentials in a secure location.
Credentials are auto-generated
Passwords and tokens are randomly generated at installation time. They are displayed once at the end of the installation. If you did not save them, use the command in the next step to redisplay them.
To redisplay the credentials at any time, run:
./run-shc.sh exec PlatformAccess
Log in to the platform
- Open your browser and navigate to the
sekoiaioURL from the credentials table (e.g.,https://app.sekoia.local/user). - Enter the
sekoiaiousername (instanceadmin@sekoia.io) in the Email field. - Enter the corresponding password in the Password field.
- Select Log in.
You are now logged in to the Administration Community. This community is dedicated to managing users and communities across your entire instance. It is not a workspace for security operations.
Community overview
Your instance contains two built-in communities after installation:
| Community | Purpose |
|---|---|
| Administration Community | Manages users and communities across the instance. Use this community for administrative tasks only. |
| sekoia community | Reserved for internal platform operations. Do not use or modify this community. |
You must create a separate community to run your security operations.
Create your community

- Select Communities in the left navigation panel.
- Select + Create in the top right corner.
- Enter a name for your community in the Name field.
- Enter a description in the Description field (optional).
- In the Administrators field, add
instanceadmin@sekoia.ioas a community administrator. - Select Create.
Your new community appears in the list alongside the two built-in communities.
Allocate your subscription
Your community has no active subscription until you import the license file provided by Sekoia.

- Select your community from the list.
- Select the Subscriptions tab.
- Select Allocate a subscription.
- Select Import a subscription.
- Select the license file provided by Sekoia for your deployment.
- Select Import.
Your subscription appears in the Subscriptions tab with its tier name, validity period, asset limit, and storage option.

Connect to your community
- Select the workspace selector in the top left corner of the interface.
- Select your community from the list.
You are now connected to your community and have access to the full Sekoia platform capabilities within your subscription scope.
Configure SSO (optional)
Sekoia Self-Hosted supports Single Sign-On via OpenID Connect. You configure SSO per community after the initial setup.
- Log in to your community.
- Navigate to Settings > SSO.
- Enter your identity provider's client ID, client secret, and authorization endpoint.
- Select Save.
Full OpenID Connect configuration documentation is available at https://docs.sekoia.io/getting_started/sso/openid_connect/.
Related links
- Deploy the platform: Deployment steps and post-deployment validation.
- Monitor your platform: How to set up alerts and dashboards for daily operations.
- Release notes v0.0.1: Feature scope and known limitations.