Skip to main content

Understand your DigiCert ONE account

Your DigiCert ONE account is your organization's top-level space for accessing and managing DigiCert services. It provides a central place to manage users, permissions, subscriptions, global settings, and environments.

Each user signs in to the same DigiCert ONE account using their own identity. Assigned permissions determine which environments, products, and settings they can access.

How your account is organized

A DigiCert ONE account contains one or more environments. Each environment is an isolated workspace where you deploy products, configure trust sources, and manage certificate workflows. Each environment is either production or demo and associated with a data residency region.

DigiCert account
├── Account settings
│   ├── Users and permissions
│   ├── Billing and subscriptions
│   └── Global configuration
│
├── Environment: Production
│   ├── Trust sources
│   └── Products
│
└── Environment: Demo or Sandbox
    ├── Trust sources
    └── Products

A DigiCert account contains account-level settings and one or more environments. Each environment can have one or more its own products and trust-source connections.

What you manage at each level

Different types of settings are managed at different levels of the platform.

Level

You manage...

Account

  • Users

  • Sign-in methods

  • Billing and subscriptions

  • Environments

  • Platform audit logs

Environment

  • Trust sources

  • Products

Solution

  • Settings

  • Resources

  • Workflows

  • Integrations

  • Solution-specific audit logs

Common account configurations

You can use DigiCert ONE in different ways depending on your requirements.

Small to Medium businesses and individuals

Small to medium businesses and individuals commonly only use CertCentral to purchase and manage publicly trusted certificates. They generally use a single production environment in their preferred region and no additional DigiCert products.

Enterprises

Enterprises commonly use:

  • Multiple environments, such as:

    • Production for live implementations

    • Demo for testing implementations and proof of concept

    • Environments for different regions to comply with regulations such as General Data Protection Regulation (GDPR)

  • One or more trust sources:

    • CertCentral for public trust

    • Private CA for private trust

  • One or more products: