Announcement: Upcoming changes to the Instaclustr Organization Owner Role
Overview
Starting November 25, 2026, NetApp Instaclustr is introducing enhancements to Instaclustr Organizations to simplify multi-account access management, strengthen organizational governance, and provide a seamless foundation for organization-level workflows such as Self-Service Bring Your Own Cloud (BYOC).
Today, Instaclustr User Roles are managed independently for each account, while the Organization feature provides a dedicated Organization Owner role for organization-level actions (such as migrating clusters between accounts or centralizing billing and support details), Organization Owners do not inherently have access to child accounts unless invited separately. These upcoming enhancements unify our access model by ensuring Organization Owners automatically receive Account Owner access across all linked member accounts.
What is Changing?
- Automatic Account Owner Access: Organization Owners will automatically receive full Account Owner access across every member account linked to the organization—with zero manual email invitations, acceptance links, or support requests required.
- Protected Governance: Account-level users can no longer remove, unlink, or modify the role of an Organization Owner from within individual account settings.
- Centralized Lifecycle Management: An Organization Owner’s membership can only be modified at the organization level via Organization Settings.
- Preserved Account Roles: Access is applied based on organizational membership rather than permanently overwriting underlying account records. If an Organization Owner is ever removed from the organization, they safely revert to any pre-existing role they held in that account.
Note: This change only applies if you are use the Instaclustr Organizations feature to manage multiple accounts.
If you operate standalone accounts without an Organization, your settings and user roles remain completely unchanged. Click here to read more about the benefits of Instaclustr Organizations and how to set one up.
Example Scenarios: What Will Happen After 25 November 2026?
To understand how this change affects Organization Owners and the linked member accounts, consider the following three scenarios:
Scenario 1: Org Owner is not currently a member of a child account
- Before: User A is an Organization Owner, but was never manually invited to “Account 3” (a member account within the organization). User A cannot view or access Account 3.
- After November 25, 2026: User A automatically gains Account Owner visibility and permissions in Account 3. No manual invitations or approvals are needed, and existing account owners are unaffected.
Scenario 2: Org Owner currently holds a restricted role (e.g., Read-Only) in a child account
- Before: User B is an Organization Owner, but was previously assigned a Read-Only User role directly within “Account 2”.
- After November 25, 2026: User B automatically inherits Account Owner access in Account 2. On the account’s Linked Users page, their entry clearly indicates they hold the Organization Owner role, and the Change Role and Unlink actions are disabled. Existing Account Owners are unaffected
Scenario 3: Removal of an Org Owner by another Org Owner
- Before: User C is an Organization owner but has only read-only role in Account 2. Removing User C from the organization via the Manage Organization Owners console does not affect their Read-Only access in Account 2.
- After November 25, 2026:
- User C automatically has Account Owner access to Account 2 because they are an Organization Owner, while their separately assigned Read-Only role remains unchanged. When removed as an Organization Owner, they lose the Account Owner access provided by that role and return to Read-Only access.
- The same principle applies to other account roles: a directly assigned Account Owner retains Account Owner access, while a user with no directly assigned role loses access to the account.
What Do You Need to Do?
On November 25, 2026, this enhancement will take effect automatically for all organizations.
Before this date, review your Organization Owners under Organization Settings → Manage Organization Owners in the Instaclustr Console. Ensure everyone holding this role should have full Account Owner access across all linked member accounts.
If an existing Organization Owner should only have access to specific accounts or needs restricted permissions (such as Read-Only or Cluster Admin), remove them from the Organization Owner role before the change takes effect. Ensure they have the appropriate directly assigned roles in the relevant accounts under Account Settings → Linked Users.
No action is required if your current Organization Owners should have Account Owner access across all member accounts.
Support
If you have questions for this upcoming change, please reach out to our support team via https://support.instaclustr.com/hc/en-us/requests/new or reach out directly to your Customer Success Manager.
Frequently Asked Questions (FAQ)
Q: Does this change affect customers without an Organization?
No. If you do not use Instaclustr Organizations, your existing account settings and user roles remain unchanged.
Q: I have Enterprise SSO / SCIM provisioning enabled. Do I need to make any changes in my Identity Provider?
No. This enhancement is fully compatible with external Identity Providers (such as Okta or Microsoft Entra ID). Because Organization Owner access does not overwrite your underlying account-level user records, your external identity synchronization will not encounter role conflicts, sync errors, or configuration drift.
Q: What happens when someone is removed as an Organization Owner?
They lose the Account Owner access provided by their Organization Owner role across all linked member accounts. Any separately assigned account role remains—for example, a directly assigned Account Owner retains Account Owner access, while a Read-Only user returns to Read-Only access.
If they have no separately assigned role in an account, they lose access to it. An Account Owner can invite them if access is still required.
Q: What should I do if a team member only needs access to one specific account and shouldn’t be an Account Owner everywhere?
Organization Ownership is intended for global administrators who require visibility and control across your entire organization. If a user only needs access to a subset of accounts or requires a restricted role (e.g., Read-Only):
- Do not assign them as an Organization Owner.
- Manage their access directly at the account level by inviting them only to the accounts they need and assigning the appropriate Account Role.
Q: How can I audit when an Organization Owner is added, modified, or removed?
All organization-level role changes, user additions, and removals are logged in the audit trail. You can review full historical details, timestamps, and the identity of the user who performed the action using the Instaclustr User Actions Audit Log in the console.
Q: What happens when a new member account is created or enrolled into the organization?
All Organization Owners automatically gain Account Owner access to that account. No separate invitations or approvals are required.
Q: Who has been notified about this upcoming change?
Advance email communications regarding this enhancement have been sent to all the Organization Support Contacts listed under your Organization.
