> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Team sign-in to GitLab, Grafana or Nextcloud

> Recipe: employees sign in to business systems through Veriqa — a server inside your network, a channel, a client for the system, and its settings from the verified section.

Your team works in GitLab, Grafana, Nextcloud or another business system, and you want employees to
sign in to it through Veriqa instead of a password. The Veriqa server runs inside your network.

<Note>
  Business systems were verified with the Email channel. On Telegram, the systems react differently to
  a missing address — see
  [The email requirement](/docs/integrations/apps#the-email-requirement-four-different-behaviors).
</Note>

## What you need

* a machine inside your network for the Veriqa server;
* a mailbox for the Email channel, or a messenger bot;
* administrator rights in the business system.

## Steps

<Steps>
  <Step title="Deploy the Veriqa server">
    Without Docker, [install it as an OS service](/docs/quickstart/os-service); in Docker, follow the
    [self-hosted quickstart](/docs/quickstart/self-hosted).
  </Step>

  <Step title="Enable a channel">
    For the verified setup, use the [Email](/docs/guides/channels#email) channel.
  </Step>

  <Step title="Declare a client for the system">
    Add the system and its `redirect_uri` to `Veriqa:OpenIddict:Clients` —
    [step 4 of the self-hosted quickstart](/docs/quickstart/self-hosted#4-declare-your-client).
  </Step>

  <Step title="Configure the system">
    Follow the section for your system on the Veriqa in business systems page:
    [GitLab](/docs/integrations/apps#gitlab), [Grafana](/docs/integrations/apps#grafana),
    [Nextcloud](/docs/integrations/apps#nextcloud) and others. Each one names the barrier and how to clear it.
  </Step>

  <Step title="Enable a quirk if the system sends extra parameters">
    If the system sends parameters that Veriqa rejects, enable a quirk for its client — see
    [Client compatibility](/docs/guides/client-compatibility).
  </Step>
</Steps>

## How to check

Sign in to the system through Veriqa and confirm the sign-in. The employee's account should be
created automatically; on Discourse, only the sign-in of an existing user was verified.

If you set up the system on your own machine first, the issuer sits in a private network, and the
system may refuse to call it. The switch for each system is listed under
[Local testing](/docs/integrations/apps#local-testing-every-system-has-its-own-switch).

## Next steps

* [Not verified](/docs/integrations/apps#not-verified) — roles, groups and other areas worth checking in
  your own setup;
* [Preparing for production](/docs/guides/hardening) — before going live;
* [Observability](/docs/guides/observability) — what to watch once the server is running.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.