> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/getting-started/create-an-account.md).
# Create an Account
## Create an Account
Lineaje supports email, third-party identity, and SAML SSO account creation.
1. Create an account with a corporate email address.
2. Sign in with GitHub, GitLab, or Bitbucket.
3. Configure SAML single sign-on (SSO) for your organization.
### Create an Account with a Corporate Email Address
1. Open the [sign-up page](https://app.veedna.com/auth/signup).
2. Select **Sign Up with Email**.
3. Enter your email address, name, and password.
4. Verify the email sent to your inbox.
5. Sign in after email verification completes.
The first user from an organization becomes its Tenant Admin. Later users require a role assignment before accessing the application.
#### Tenant Admin and Standard Users
The first user who registers for an organization becomes the Tenant Admin. Tenant Admins add users and assign roles within their organization. See [Organization and User Management](/getting-started/organization-and-user-management.md).
Subsequent users are created without a role. They may see a **Request Permission** message. A Tenant Admin must assign a role before these users can access Lineaje.
#### Approve a User
Tenant Admins approve pending users as follows:
1. Open **Settings** → **User Management** → **Users**.
2. Select the pending user.
3. Assign an SBOM360 role and organization.
### Create an Account with GitHub, GitLab, or Bitbucket
Use an existing GitHub, GitLab, or Bitbucket account to sign in.
1. Open the [sign-in page](https://app.veedna.com/auth/signin).
2. Select GitHub, GitLab, or Bitbucket.
3. Authorize Lineaje when prompted.
4. Complete the provider's sign-in flow.
On first sign-in, you become the Tenant Admin for the new tenant. Invite additional users from **Settings** → **User Management** → **Users** → **Invite User**.
Invited users receive an email link. They sign in with their existing GitHub, GitLab, or Bitbucket credentials.
### Configure SAML Single Sign-On
Configure SAML SSO after creating a corporate email account. This account becomes the Tenant Admin.
1. [Create an account with a corporate email address](#create-an-account-with-a-corporate-email-address).
2. Sign in with the new account.
3. Open **Settings** → **Authentication**.
4. Select **Edit Configuration** → **Single Sign-On**.
5. Enter the sign-in URL and upload the SAML `.cer` certificate.
6. Select **Enable SSO**.
See the [Azure AD configuration example](/getting-started/create-an-account/configure-azure-ad-for-sso.md) and [Okta configuration example](/getting-started/create-an-account/configure-okta-for-sso.md).
#### SSO Initiation Methods
Lineaje supports service provider (SP)-initiated SSO. Lineaje redirects users to the identity provider for authentication.
Identity provider (IdP)-initiated SSO is disabled by default. It has known security risks. Contact if your organization requires it.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.veedna.com/getting-started/create-an-account.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
