Oracle Cloud Infrastructure IAM policies define which groups can manage Fusion Data Intelligence resources in a compartment. Learn how these permissions support tasks such as creating, updating, and deleting resources—and why network rules and data retention settings serve a different purpose.

Multiple Choice

In Oracle Cloud Infrastructure (OCI), what are the policies that grant a group permission to manage FDI resources within a compartment?

In OCI, access control is managed with IAM policies. These policies define who (groups, users, or service principals) can do what on which resources within a compartment. To let a group manage FDI resources in a specific compartment, you create a policy that grants that group the appropriate level of access to FDI resources in that compartment. For example, a policy could state that the group is allowed to manage all FDI resources in that compartment, enabling members to create, update, and delete those resources as needed. Other options don’t grant this kind of resource-management permission: data retention policies control how long data is kept, network security group rules govern network traffic rather than who can manage resources, and audit policies relate to auditing behavior rather than access rights.

How OCI IAM Policies Control Oracle Fusion Data Intelligence

Oracle Fusion Data Intelligence (FDI) brings analytics and business insight together, but its resources still need careful access control. In Oracle Cloud Infrastructure (OCI), that control comes from Identity and Access Management policies. A policy tells OCI who may take which actions on which resources—and where those permissions apply.

That may sound like a small administrative detail. It isn’t. A well-scoped policy lets the right team manage an FDI environment without handing out broad access across the tenancy. It also makes responsibilities easier to understand when people join, change roles, or leave.

The policy is the rulebook

OCI policies are written statements that grant permissions to identities, such as groups or users. A policy typically answers three questions:

  • Who gets access? For example, an IAM group.

  • What can they do? For example, manage a resource family.

  • Where can they do it? For example, within a named compartment.

For FDI resource management, the relevant mechanism is an IAM policy. Data retention settings, network security group rules, and audit controls have their own jobs, but they don’t grant a group permission to create or manage FDI resources.

Think of a policy as a key with a label. The label says who can use it, which doors it opens, and which building it belongs to. If the label is too broad, the key may open more doors than intended. If it’s too narrow, the team may be blocked from routine work.

Why compartments matter

A compartment is a logical container for OCI resources. Organizations use compartments to separate workloads, teams, or stages of operation. One compartment might hold production resources, while another holds development resources. That separation helps administrators set clear boundaries.

Policies can be attached at different levels of the OCI hierarchy. A policy defined higher up may cover resources in compartments below it, depending on its scope. A policy targeted at one compartment is more limited. That’s often the cleaner choice when a group only needs to manage FDI resources in a particular environment.

For example, a group responsible for an analytics project may need broad control over FDI resources in the project’s compartment—but not over unrelated cloud services or another team’s production environment. The compartment gives the policy a boundary.

Reading an FDI policy statement

An OCI policy uses a standard structure. A simplified example for a group that needs to manage FDI resources in a compartment looks like this:


Allow group FDI-Admins to manage fdi-family in compartment Analytics

Read it from left to right:

  • Allow grants permission.

  • group FDI-Admins identifies the group receiving it.

  • to manage sets the level of access.

  • fdi-family identifies the relevant FDI resource family.

  • in compartment Analytics limits the scope to that compartment.

The manage verb is a broad permission level. It generally covers management actions such as creating, updating, and deleting supported resources, along with lower-level access needed to work with them. That makes it suitable for administrators who own the FDI environment, but it may be too much for someone who only needs to view information or use a service.

OCI offers different permission verbs, including inspect, read, use, and manage. Their precise effects depend on the resource type and the operations exposed by that service. In plain terms, they range from viewing basic resource details to carrying out management tasks. Choosing the narrowest suitable verb is a simple way to reduce risk.

The example is illustrative. Policy resource names and available permissions can change as OCI services evolve, so administrators should check Oracle’s current FDI and IAM documentation before deploying a policy.

Groups make access easier to govern

Policies can grant permissions to individual users, but groups are usually easier to manage over time. Instead of editing policies whenever a staff member changes roles, an administrator can add or remove that person from the relevant group.

Imagine a group called FDI-Admins. Members of that group might own workspace configuration and resource lifecycle tasks. A separate group, such as FDI-Readers, could receive a lower level of access for people who need visibility but don’t need to change settings. The exact policy statements depend on the tasks and resource types involved.

This group-based approach keeps the policy focused on roles rather than names. It also makes reviews less of a scavenger hunt: an administrator can examine a small set of group policies and membership lists instead of tracking permissions scattered across individual accounts.

Least privilege: enough access, not a blank cheque

Granting manage access is convenient, but convenience shouldn’t be the only factor. If a group only needs to view FDI resources, a broad management grant may give members more authority than their work requires. That can increase the impact of a mistaken change or compromised account.

A sensible policy design starts with the job to be done. Ask what the group needs to see, change, create, or remove. Then grant the smallest permission level and scope that supports those tasks. If requirements change, the policy can change too.

This is not about making routine work harder. It’s about keeping authority close to responsibility. An FDI administrator may need to manage resources; a business stakeholder who reads dashboards may not. One service, several roles, different levels of access.

Policies aren’t network rules or data controls

OCI includes several kinds of controls, and their names can sound similar in a busy cloud console. Their functions are distinct:

  • IAM policies govern which identities can access or manage cloud resources.

  • Data retention policies govern how long certain data is kept.

  • Network security group rules control permitted network traffic.

  • Audit controls and logs help record or review activity.

These controls can work together, but they don’t replace one another. A network rule might allow traffic to reach a service endpoint; it doesn’t automatically authorize a person to manage the FDI resource. Likewise, an audit record can show that an action occurred, but it doesn’t grant permission to take that action.

That distinction is useful when troubleshooting. If a team member can reach a service but can’t create or update an FDI resource, the issue may be an IAM policy or group membership—not a network rule. If they can manage resources but can’t connect to an endpoint, network configuration may be the next place to look.

A few checks before a policy goes live

Before applying an FDI policy, confirm that the group exists, that its membership reflects the intended role, and that the compartment name is correct. Then check the resource family and permission verb against Oracle’s current documentation.

It also helps to keep policy statements readable. Descriptive group and compartment names make intent easier to spot during a review. Avoid granting access at a broader tenancy level when a single compartment will do, and revisit policies when teams or responsibilities change.

Finally, remember that policy changes may not appear instantly everywhere. Allow time for OCI to apply the change, then verify access with an appropriate account and the actual tasks the group needs to perform.

Clear access starts with clear boundaries

For OCI-managed FDI resources, IAM policies are the mechanism that grants a group permission to act. They connect an identity to a set of actions and a resource scope. With a compartment boundary and a carefully chosen permission level, an organization can give FDI teams the authority they need while keeping unrelated resources out of reach.

That’s the practical value of a good policy: not just saying “yes” or “no,” but making it clear who can do what, and where.