Product guide

From first workspace to managed deployment

Use these practical paths to configure SignaGenius safely. Provider-specific activation still requires an administrator in the relevant Google, Microsoft, DNS, billing, or delivery account.

1. Create the workspace

Define the primary domain, organization hierarchy, inherited brand data, and administrator access.

  • Choose the default entity
  • Set permissions and entity scope
  • Review security policy

2. Add managed users

Create users individually or use validated CSV, XLSX, published Google Sheet, directory, or SFTP import paths.

  • Run a dry preview
  • Resolve seat-capacity errors
  • Review row-level outcomes

3. Build signatures

Create scenario-aware templates, preview with a real managed user, assign targets, and publish deliberately.

  • Use structured blocks
  • Test conditions and fallbacks
  • Queue a delivery test

4. Launch campaigns

Upload safe banner media, configure audiences and recipient rules, add UTM attribution, and schedule activation.

Administrator required

5. Activate a provider

Supply the required provider credentials, verify requested scopes, run a limited test group, and inspect synchronization history.

Troubleshooting

Start with audit events, connector health, the latest job’s row outcomes, agent telemetry, and delivery retry history.

  • Never paste secrets into support messages
  • Revoke exposed keys immediately
  • Use test entities before broad rollout