Skip to content

Setup overview

The topics in this section walk you through the steps required to configure Code Sign Manager - SaaS for use in your environment.

If you have not yet reviewed the conceptual material or completed a tutorial, consider starting with:

  • Solution overview — Learn how Code Sign Manager - SaaS works and how the core components fit together.
  • Choosing a signing workflow — Understand when to use user-based authentication versus service account authentication.
  • Tutorials — Follow a guided workflow to see the full signing lifecycle in action.

Once you are ready to configure your environment directly, use the table below to determine which setup tasks you need to complete.

Setup tasks at a glance

Task Who performs it Required? When you need it
Onboard users Administrator Always Before any user or service account can be assigned to a Project or use a Signing Key.
Create a team Administrator Optional When a group of users or a service account should share the same signing permissions. Also required if using service accounts.
Create a service account Administrator Optional Required only for machine-based or automated signing (CI/CD). Not needed for user-based signing.
Configure a CA Administrator Optional Required only if you plan to issue certificates from Microsoft AD CS, DigiCert, or ZTPKI. Not required for “None” or “Built-in CA.”
Create a Project Administrator Always Required to organize signing keys and assign Authorized Signers.
Create a Signing Key Administrator Always Required to generate the keys and certificates used by users or automated systems.
Install Code Sign Client Authorized Signer or CI operator Always (to sign) Must be completed on any signing machine before authentication or signing can occur.