> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/administration/account-management.md).

# Account Management

Create your Konvu account, configure authentication, and manage team members.

Konvu accounts are organized around **organizations**. Each organization has its own integrations, repositories, assessment settings, and team of users. This page covers how to create an account, authenticate, and manage your team.

## Creating an account

When you sign up and log in for the first time, Konvu automatically creates an organization for you. Your organization name is derived from your email domain -- you can rename it later from the dashboard.

New organizations receive **a defined trial assessment credits** to get started. See [Assessment Credits](/konvu/administration/assessment-credits.md) for details on how credits work.

To request an account or get help with setup, contact [support@konvu.com](mailto:support@konvu.com?subject=Konvu%20Account).

## Authentication methods

Konvu uses [Zitadel](https://zitadel.com/) as its identity platform. You have several options for logging in:

### Passwordless authentication

You can authenticate without a password using:

* **Passkeys** -- FIDO2/WebAuthn-based authentication via fingerprint, face recognition, or hardware security keys
* **One-Time Passwords (OTP)** -- time-based codes sent to your authenticator app

### Multifactor authentication (MFA)

Enable MFA to add a second factor to your login. Supported second factors:

* Authenticator app (TOTP)
* Fingerprint or biometric
* Hardware security keys (FIDO2/U2F)

{% hint style="info" %}
MFA configuration is managed per user through the Zitadel login flow. You configure it during your first login or from your account settings.
{% endhint %}

## Identity providers

Konvu supports external identity providers so your team can log in with existing credentials. The following providers are available:

| Provider                    | Notes                                    |
| --------------------------- | ---------------------------------------- |
| **Google**                  | Google Workspace and personal accounts   |
| **GitHub**                  | Cloud and Enterprise Server              |
| **GitLab**                  | Cloud and Self-Hosted                    |
| **Microsoft**               | Azure AD / Entra ID                      |
| **Active Directory / LDAP** | On-premises directory services           |
| **SAML**                    | Any SAML 2.0-compliant identity provider |

To configure an identity provider for your organization, contact [support@konvu.com](mailto:support@konvu.com?subject=Identity%20Provider%20Setup). The Konvu team will set up the connection on your Zitadel organization.

## Managing your team

You manage team members from **Configuration > Team** in the Konvu dashboard. From this page you can:

* **Invite users** -- enter their email, first name, and last name. The user receives a verification email to set up their account.
* **Resend invitations** -- if a user hasn't completed their verification, resend the invitation email.
* **Deactivate users** -- revoke a user's access so they can no longer log in. Their data is preserved.
* **Reactivate users** -- restore access for a previously deactivated user.

Each user is associated with exactly one organization. A user who already belongs to a different organization cannot be invited to yours.

### User states

| State        | Meaning                                                       |
| ------------ | ------------------------------------------------------------- |
| **Pending**  | User was invited but hasn't verified their email yet          |
| **Active**   | User has verified their email and can log in                  |
| **Inactive** | User was deactivated by an admin                              |
| **Locked**   | User account is locked (e.g., too many failed login attempts) |

## Next steps

* [Assessment Settings](/konvu/administration/assessment-settings.md): Configure OpenAI keys (BYOK), code evidence collection, and per-repository assessment settings
* [Assessment Credits](/konvu/administration/assessment-credits.md): Understand how credits are consumed and monitor usage


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konvu.com/konvu/administration/account-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.