Request Authorization Before Acting on an Account Change

Separate the requested change from the authority to request it

A clear instruction is not the same as clear authority. Someone may know exactly which mailbox should be changed without having permission to approve the change. Before acting, identify what would change and who is permitted to authorize that kind of change under your organization’s process.

Pay particular attention to changes that affect access, recovery details, mailbox administration, or where messages are delivered. If the request is outside your normal process, comes from an unfamiliar address, or conflicts with existing ownership information, treat that uncertainty as a reason to stop—not as a reason to investigate by making a partial change.

For BITTU Mail workspace or domain administration, the ability to perform an action can depend on role, plan, and provisioning state, and permissions are enforced server-side. Use an authorized workspace or domain administrator for actions that require those permissions; do not assume that a requester's job title or ability to send a message grants access.

Pause in a way that is visible and specific

A useful pause tells the requester what is on hold, why it is on hold, and what must happen next. Avoid vague replies such as “I’ll check” that can leave others expecting the change to proceed. Do not make a temporary version of the change while waiting; partial changes can create the same risks as completing it.

Keep the request’s owner responsible for obtaining approval and restarting the work. You can identify the missing confirmation and explain how to provide it, but do not silently take ownership of chasing an approver or decide that no response means approval. If the owner is unavailable, follow the organization’s established escalation process rather than choosing a substitute approver yourself.

Hi [requester name],
I’ve paused the requested change to [account or mailbox] because I can’t yet confirm that you’re authorized to approve it. Please ask [known approver or role] to confirm the specific change through [trusted channel]. I have not changed the account. You own this request; reply here once the confirmation is available, and I’ll resume the work.

Ask for confirmation that answers the actual question

Request confirmation from a person or role already recognized as authorized for that change. Use a trusted contact method already on file or an established internal channel, not new contact details supplied only in the questionable request. If your normal process requires a second approver or a recorded ticket, follow that process.

The confirmation should identify the account or mailbox, describe the requested change, and clearly approve it. For example, “I approve changing [mailbox] recovery contact to [new contact]” is more useful than “Looks fine.” Keep the confirmation with the request according to your normal recordkeeping process. Do not ask anyone to send a password or one-time passcode as proof of authority; those credentials should not be shared.

• Which account or mailbox is affected?
• What exact change is being approved?
• Who is confirming, and are they authorized under the applicable process?
• Where will the confirmation be recorded?

Avoid collecting more information than you need

A pause is not a reason to request sensitive information. Ask for approval of the change, not passwords, one-time codes, or unnecessary personal details. If the proposed change includes a new contact address or destination, verify the authorization through a trusted route before entering it.

Keep the conversation neutral. You do not need to accuse the requester of wrongdoing; simply state that you cannot proceed until the required authority is confirmed. This keeps the exchange professional and avoids disclosing information about account controls to someone whose authority is still uncertain.

Resume only after the missing step is complete

When confirmation arrives, compare it with the original request. Check that the authorized person approved the same account and the same change—not a similar request with a different destination or broader access. If any detail differs, pause again and ask the request owner to resolve the discrepancy.

After the change is made, tell the owner what was completed and ask them to verify the intended outcome using their normal account process. Do not claim success before the action is complete, and do not imply that an email message alone proves a change took effect. If the action is unavailable to your role or the account is not provisioned for it, refer it to the appropriate administrator instead of improvising.

A quick handoff check

Before closing or handing off the request, make sure the next person can see both the hold and the condition for resuming. A concise note prevents a colleague from treating the original request as approval and makes the request owner’s responsibility explicit.

• Change remains unapplied while authority is unclear.
• The required approver and trusted confirmation route are identified.
• The request owner knows they must return with confirmation and ask to resume.
• After completion, the owner receives a factual status and can check the intended result.

Request: [requested account change]
Status: Paused; no change made.
Awaiting: Confirmation from [authorized approver or role] via [trusted channel].
Owner: [request owner] to provide confirmation and request resumption.