Create a Debricked account

Create your Debricked account effortlessly. Follow this simple guide to set up your account quickly.

You must create a Debricked account to use our service. To create a Debricked account, navigate to our website and click Start for Free or Log in.

There are two ways to create a Debricked account:

• Sign up with email

• Sign up using GitHub SSO

Sign up with email​​​​​​​

This process creates a new company account. To join an existing company account, contact your company administrator for assistance.

To sign up using your email address:

1. Type your email address.

2. Read and accept the privacy policy and terms and conditions.

3. Type your details.

4. Type a secure password for your account.

Sign up using GitHub SSO

You can also sign up using your GitHub account:

1. Click the GitHub button on the Sign-up page.

2. Sign in using your GitHub credentials.

3. Next, you can either choose to connect to an organization or continue without one.

   • If your company or colleagues already use Debricked, join the existing organization.

   • If you are the first collaborator to join or prefer to use our tool privately, you can opt to continue without connecting to an organization.

4. Choose the email address you want to use with your Debricked account and enter your information.

5. Create a secure password.

   • The password will not be used if you are logging in through GitHub.

   • The password is used to access admin pages if you have administrative rights.

   • The password is used if you use the email to log in instead of using the GitHub Single Sign-On (SSO).

Administrator role

If you are the first collaborator to sign up in our organization or if you are not associated with any organization, you will receive admin rights. Even if you sign up using Single Sign-On (SSO), you will still need to create a password for the admin interface due to handling of sensitive information.

As an administrator, you are allowed to:

• Add, remove, or edit users

• Manage access tokens

• Change user permissions such as:

  • Allow SSO

  • Enforce comments when marking vulnerabilities as unaffected

  • Allow users to snooze vulnerability automations