Google Workspace delegated mailbox: verify application support separately

Define the decision

Gmail delegation is a provider feature with its own permission model. Zintara’s ordinary OAuth connection identifies the authorizing account; the reviewed flow does not expose a separate delegated-mailbox selector.

Work through the procedure

1. Identify the account signing in and the mailbox the team intends to operate.
2. Confirm delegation works in the provider’s supported interface.
3. Check whether the application supports choosing that delegated identity.
4. If it does not, use an explicitly supported mailbox arrangement approved by the administrator.

Worked example

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

User signs in: [email protected]
Delegated webmail access: [email protected]
Application connected identity: [email protected]
Missing capability: explicit delegated sales mailbox selection

Read the result

The distinction prevents accidentally sending a campaign from the assistant’s own address or expecting replies from an inaccessible mailbox. Access in one client does not imply the same access path in every client.

Check before moving on

1. Inspect a controlled received message’s sender identity.
2. Verify which mailbox contains the reply.

Limits and next action

Do not share the mailbox owner’s password to imitate delegation. Choose a supported arrangement with accountable ownership and current administrator approval.

Source: Google: delegate and collaborate on email