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

# Group Management

**Groups** in CERTInext provide a structured way to organize users, certificate requests, products, and financial controls within a single account. They act as logical boundaries that help enterprises delegate responsibility, apply scoped access, and manage certificate operations at scale - without fragmenting governance or visibility.

Groups are especially useful in multi-team, multi-application, or multi-entity environments where different users should be able to request and manage certificates only within defined limits.

<figure><img src="https://955357252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNvYrWQTJxwzOAGkanyHW%2Fuploads%2FYEGIJSzbW9hD1SACvo8P%2Fimage.png?alt=media&amp;token=34baed5b-1dff-444b-a9f9-585cfea77f39" alt=""><figcaption></figcaption></figure>

#### Purpose of Groups

Groups are used to:

* Segment certificate operations by team, project, application, or business unit
* Control which users can access and operate within a specific scope
* Restrict which organizations, domains, and products can be used for certificate requests
* Apply financial controls such as balance usage and cost attribution
* Route notifications and renewal communications appropriately

This allows decentralized operations while maintaining centralized governance.

#### Group Configuration

Each group in CERTInext has clearly defined configuration attributes:

**Group Information**

Defines the identity and ownership of the group, including:

* Group name and description
* Group logo (optional)
* Creator details and creation timestamp
* Source IP used during creation

This information helps with traceability and administrative oversight.

#### User Access Control

Groups can be configured to:

* **Allow specific users** to access the group
* Assign users specific **roles** within the group

Only authorized users can view, request, or manage certificates within that group’s scope, supporting least-privilege access and separation of duties.

#### Certificate Request Scope

Groups define *what certificates can be requested* and *for whom*:

* **Organizations**\
  Restrict certificate requests to specific validated organizations.
* **Domains**\
  Limit certificate issuance to approved domains associated with the group.
* **Products**\
  Control which certificate products or profiles are available to users in the group.

This prevents accidental or unauthorized certificate issuance outside approved boundaries.

#### Financial Controls

Groups can be linked to specific financial handling rules, such as:

* Deducting certificate costs from the account balance
* Supporting cost segregation across teams or projects
* Enabling internal chargeback or cost tracking models

These controls are especially valuable in large organizations with shared certificate budgets.

#### Notifications and Renewal Communication

Groups support configuration of:

* Certificate renewal notification email addresses
* Group-specific communication for lifecycle events

This ensures renewal alerts and operational messages reach the right stakeholders without over-notifying unrelated teams.

#### User Membership and Roles

Each group maintains a list of assigned users, including:

* User identity and contact details
* Role within the group (e.g., administrator, operator)
* Account status and creation date

This provides transparency into who is responsible for certificate operations within the group.

#### Why Groups Matter

Without grouping, certificate platforms can quickly become difficult to govern in large or distributed organizations. Groups enable:

* Controlled decentralization of certificate requests
* Reduced operational risk through scoped access
* Clear ownership and accountability
* Simplified administration at enterprise scale

#### Groups as an Operational Boundary

In CertiNext, groups function as **operational trust boundaries**. They allow organizations to scale certificate management across teams and use cases while preserving strong governance, auditability, and financial control - making groups a foundational construct for enterprise deployments.
