You're viewing OCI IAM documentation for new tenancies in regions that have been updated to use identity domains.

Details for the Email Delivery Service

This topic covers details for writing policies to control access to the Email Delivery service.

Resource-Types

email-domains

email-work-requests

email-family

approved-senders

suppressions

Supported Variables

The Email Delivery Service supports all the general variables (see General Variables for All Requests), plus the ones listed here.

Variable Variable Type Comments
target.approved-sender.email-domain String The value matches the domain portion (right-hand-side) of the email address and the name of the associated email-domain object if one exists. Policies should use the U-label form of the domain. Matching is case-insensitive. This is not available for ListSenders.
target.email-domain.name String Scopes permission to domains that match the specified domain name. Policies should use the U-label form of the domain. Matching is case-insensitive. This variable can be used with pattern matching syntax to grant sub-domain access. This is not available for ListEmailDomains.
target.email-domain.id Entity (OCID) Not available for ListEmailDomains or CreateEmailDomain.
target.email-work-request.id Entity (OCID) Not available for ListWorkRequests.
target.approved-sender.id Entity (OCID) Not available for ListSenders and CreateSenders.
target.approved-sender.emailaddress String Not available for ListSenders.
target.dkim.email-domain String Scopes permission to DKIMs for a specific email domain. Policies should use the U-label form of the domain and matching is case-insensitive. Not for ListDkims.

Details for Verb + Resource-Type Combinations

The following tables show the permissions and API operations covered by each verb. The level of access is cumulative as you go from inspect > read > use > manage. For example, a group that can use a resource can also inspect and read that resource. A plus sign (+) in a table cell indicates incremental access compared to the cell directly above it, whereas "no extra" indicates no incremental access.

Permissions Required for Each API Operation

The following table lists the API operations in a logical order, grouped by resource type.

For information about permissions, see Permissions.

API Operation Permissions Required to Use the Operation
GetEmailConfiguration EMAIL_CONFIGURATION_READ
ListEmailDomains EMAIL_DOMAIN_INSPECT
GetEmailDomain EMAIL_DOMAIN_READ
CreateEmailDomain EMAIL_DOMAIN_CREATE
UpdateEmailDomain EMAIL_DOMAIN_UPDATE
DeleteEmailDomain EMAIL_DOMAIN_DELETE
ChangeEmailDomainCompartment EMAIL_DOMAIN_MOVE
ListSenders APPROVED_SENDER_INSPECT
GetSender APPROVED_SENDER_READ
CreateSender APPROVED_SENDER_CREATE
UpdateSender APPROVED_SENDER_UPDATE
DeleteSender APPROVED_SENDER_DELETE
MoveSender APPROVED_SENDER_MOVE
SmtpSend APPROVED_SENDER_USE
ListSuppression SUPPRESSION_INSPECT
GetSuppression SUPPRESSION_READ
CreateSuppression SUPPRESSION_CREATE
DeleteSuppression SUPPRESSION_DELETE
ListWorkRequests EMAIL_WORK_REQUEST_INSPECT
GetWorkRequest EMAIL_WORK_REQUEST_READ
ListWorkRequestErrors EMAIL_WORK_REQUEST_INSPECT
ListWorkRequestLogs EMAIL_WORK_REQUEST_INSPECT
CreateEmailReturnPath EMAIL_RETURN_PATH_CREATE
DeleteEmailReturnPath EMAIL_RETURN_PATH_DELETE
GetEmailReturnPath EMAIL_RETURN_PATH_READ
ListEmailReturnPath EMAIL_RETURN_PATH_INSPECT
UpdateEmailReturnPath EMAIL_RETURN_PATH_UPDATE