Message Center
The Organizations service provides Service Control Policies (SCPs) for access control.
SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.
This section describes the elements used by Organizations SCPs. The elements include actions, resources, and conditions.
For details about how to use these elements to edit a custom SCP policy, see Creating an SCP.
Actions
Actions are specific operations that are allowed or denied in an SCP.
- The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an SCP.
- The Resource Type column indicates whether the action supports resource-level permissions. Actions supported by Message Center are valid for all resources. You can use a wildcard (*) to indicate all resource types.
- The Condition Key column contains keys that you can specify in the Condition element of an SCP statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
The following table lists the actions that you can define in SCPs for Message Center.
Action |
Grants Permission To |
Access Level |
Resource Type (*: required) |
Condition Key |
---|---|---|---|---|
messageCenter:financeMsg:view |
|
read |
* |
N/A |
messageCenter:financeMsg:subscribe |
|
write |
* |
N/A |
messageCenter:financeMsg:delete |
|
read |
* |
N/A |
messageCenter:filingMsg:view |
|
read |
* |
N/A |
messageCenter:filingMsg:subscribe |
|
write |
* |
N/A |
messageCenter:filingMsg:delete |
|
read |
* |
N/A |
messageCenter:contractMsg:view |
|
read |
* |
N/A |
messageCenter:contractMsg:subscribe |
|
write |
* |
N/A |
messageCenter:contractMsg:delete |
|
read |
* |
N/A |
messageCenter:campaignsMsg:view |
|
read |
* |
N/A |
messageCenter:campaignsMsg:subscribe |
|
write |
* |
N/A |
messageCenter:campaignsMsg:delete |
|
read |
* |
N/A |
messageCenter:productMsg:view |
|
read |
* |
N/A |
messageCenter:productMsg:subscribe |
|
write |
* |
N/A |
messageCenter:productMsg:delete |
|
read |
* |
N/A |
messageCenter:omMsg:view |
|
read |
* |
N/A |
messageCenter:omMsg:subscribe |
|
write |
* |
N/A |
messageCenter:omMsg:delete |
|
read |
* |
N/A |
messageCenter:securityMsg:view |
|
read |
* |
N/A |
messageCenter:securityMsg:subscribe |
|
write |
* |
N/A |
messageCenter:securityMsg:delete |
|
read |
* |
N/A |
messageCenter:recipient:view |
|
read |
* |
N/A |
messageCenter:recipient:update |
|
write |
* |
N/A |
Resources
Message Center does not support resource-specific permission control in SCPs. If you want to allow access to Message Center, use the wildcard (*) for the Resource element to apply SCPs to all resources.
Conditions
Message Center does not support service-specific condition keys in SCPs. It can only use global condition keys applicable to all services. For details, see Global Condition Keys.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot