Mailbox ownership and team access: verify workspace scope and sender authority

Define the decision

Zintara's current mailbox list and detail queries are scoped to the active workspace. The provider's account authorization and the team's internal responsibilities still need explicit review. Avoid using a shared password or a spreadsheet of credentials as a substitute for a supported access process.

Work through the procedure

1. Identify the authorized provider account owner and the purpose of connecting the mailbox.
2. Verify which workspace contains the connection and which team members have appropriate access.
3. Assign responsibility for sender settings, reply review and credential recovery.
4. Review access when people change roles or leave, using the provider and application's supported controls.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Access review
Provider owner: authorized mailbox holder
Application scope: selected workspace
Sending responsibility: campaign operator
Reply responsibility: named inbox owner
Recovery responsibility: authorized account administrator
Unverified assumption: every team member has identical rights because the mailbox appears in a shared process document.

Read the result

The review makes it possible to change responsibilities without exposing credentials or impersonating a sender. A person who handles replies may not need authority to replace authentication details. Confirm actual permissions instead of treating a role label in a planning document as an enforced control.

Check before moving on

1. Keep secrets out of campaign notes and exports.
2. Verify the active workspace before connecting or editing a mailbox.
3. Review sender display name and signature for truthful identity.

Limits and next action

These scope statements were checked against current mailbox queries and connection handling. This guide does not promise per-mailbox access controls beyond implemented workspace permissions. Provider delegation and organizational authorization require their own appropriate review.

Source: Zintara product context; procedures and examples are editorial guidance