Agenteous·
Operator Console

Operators, Inboxes and Known Senders

What It's For

These three screens record who may operate your Agenteous install, which mail provider the agents use, and which senders you trust. Operators & Roles grants each operator a role, Email Inboxes shows the mail provider the agents send through, and Known Senders keeps a list of trusted sender domains. In the Operator Console, under Agency, open Operators & Roles or Email Inboxes; Known Senders is not listed in the sidebar and is reached by its direct link.

Operators & Roles

The page header reads Staff. Across the top, three counts summarize access: People (operator emails mapped to a role), Distinct roles (how many different roles are in use) and Separation-of-duties overrides (tighter rules on specific actions).

Role Assignments

One row per operator: their work email and the role they hold. The email must match the one you sign in with. The role decides which actions that person can take in the console. The roles you will use most are:

  • Ops Admin: runs the install's configuration, connections and users.
  • Admin Operator: an administrator who also does the daily work; it combines Ops Admin and Marketing Operator without the compliance powers.
  • CCO: the compliance officer; edits governance rules and approves exceptions, and also holds the administrator permissions.
  • Marketing Operator: runs the marketing content lifecycle, proof points, ICP refinements, CRM enrichment and prospecting.
  • Compliance Reviewer: approves exceptions and reads the audit log.
  • Viewer: read-only access, for executives and auditors.

Click Edit (or Configure staff when no access is set up yet), use Add assignment and Remove, then Save Changes. Every role is checked against the role list, so an unknown role is refused.

Separation-of-duties Overrides, Group Mapping and Slack Users

Separation-of-duties overrides (for example spend limits or dual-approval rules), Identity-provider group mapping (which sign-in group becomes which role) and Slack user mapping (which Slack user each operator is) are shown for reference only. Saving the page leaves them untouched.

If the page shows No Staff Access Set Up Yet, role-based access has not been set up for this install.

Email Inboxes

Mail Provider

A read-only card naming the provider the agents use for outbound mail and drafts, with Configured or Not configured for its credentials. You set those credentials on Connections; this card only shows whether they exist.

Known Senders

A list of trusted sender domains and addresses. It starts from the company domains in your CRM, leaving out public mail providers and your own domain, and adds or removes entries you set by hand. Two counts sit at the top: Known senders and Matching filter. Type in the filter box to search; the list shows the first 300 matches.

Click Manage to edit. Under Add senders, type @domain.com to trust a whole domain or paste full email addresses, separated by spaces, commas or new lines, then click Add to allowlist. Remove an entry with the button on its row; removals take effect at once. Click Done when you finish.

The list is recorded but does not yet filter mail: messages from other senders still reach the agents. The senders that inbox triage never files away are set separately, on Inbox Triage under Never Filed Away.

Who Uses It

  • Ops Admin, Admin Operator, CCO: assign roles and edit the known senders list. Only these roles can save on these screens, and every save is recorded in the Audit Log.
  • Everyone else: has no reason to visit; these screens change access for the whole install.