# Get started with Vigilbase OS

> Sign in with Vigilbase Identity, set up your organisation, invite members and connect your first provider.

Source: https://docs.vigilbase.com/os/getting-started

This page takes you from your first sign-in to your first connected provider. You need a Vigilbase account with a verified email address.

## Sign in

:::steps
1. **Go to `https://os.vigilbase.com`.**
2. **Choose Sign in with Vigilbase Identity.** You sign in on Vigilbase Identity with your Vigilbase account, then return to OS.
3. **Confirm your second factor if asked.** Owners, and anyone with privileged permissions such as approving actions, must use multi-factor authentication. If you have not set it up, choose **Set up authenticator**, enrol an authenticator app in Vigilbase Identity, then choose **Confirm after setup**. A passkey sign-in on its own does not satisfy multi-factor authentication in OS.
:::

If sign-in does not finish, the page says why, for example that your email is not verified or that the link was already used, and offers **Sign in again**.

## Set up your organisation

Each organisation in OS is a separate, isolated workspace. Organisations and memberships live in Vigilbase Identity.

- **Your organisation already exists.** OS opens it. If you belong to several, use the organisation switcher at the top of the sidebar to change organisation. It shows your role in each.
- **You need a new organisation.** On **Create your organisation**, choose **Create organisation**. You create it in Vigilbase Identity and return to OS.

Only an owner or admin can set up an organisation in OS for the first time. If you see that message, ask an owner or admin to sign in first, or create your own organisation.

A new organisation has no data until you connect a provider. Vigilbase never adds sample data to a production organisation.

## Invite members

You need the `members.manage` permission, which owners have.

:::steps
1. **Open Settings, then Members.**
2. **Choose Invite.**
3. **Enter the Email and choose a Role.** Roles are **Owner**, **Admin** and **Viewer**; new members are Viewers by default.
4. **Choose Send invitation.** Vigilbase Identity sends the invitation email. You confirm it's you with your authenticator first.
:::

Admins need explicit grants to approve actions. To give someone analyst, approver or auditor rights, add a scoped grant. See [Members and grants](https://docs.vigilbase.com/os/settings/members).

## Connect your first integration

You need the `integration.manage` and `credential.manage` permissions.

:::steps
1. **Open Integrations and choose Add connection.**
2. **Select a provider.** Providers marked **One-click** connect by signing in to the provider or running a guided setup, with no API keys to copy.
3. **Choose the access level.** **Read and write** lets Vigilbase propose response actions; nothing changes until someone approves a plan. **Read only** means Vigilbase only reads, and you can add write access later.
4. **Follow the provider's steps.** For example, choose **Continue with Cloudflare** and approve access on Cloudflare's screen.
5. **Choose datasets.** Pick what to collect and start collecting.
:::

Health, lag and volume appear on the connection as data arrives. Until then, coverage shows as unknown, never as healthy. See [Integrations](https://docs.vigilbase.com/os/integrations) for every provider and [Cloudflare](https://docs.vigilbase.com/os/integrations/cloudflare) for a worked example.

## Next steps

:::cards
- [Overview](https://docs.vigilbase.com/os/overview) See what needs you.
- [Posture](https://docs.vigilbase.com/os/posture) Check which detections can run on your data.
- [Approvals and policy](https://docs.vigilbase.com/os/concepts/approvals-and-policy) Decide who may approve changes.
:::