Integrations Configuration: Recommended Permissions and Best Practices

Summary

The following settings represent best practices designed to cover most standard setups. Because each i-Hub solution is uniquely tailored to your specific functionality and workflow, requirements may vary slightly between builds.

For the most seamless experience, we recommend that an administrator performs the initial configuration. While a sub-admin may be used if granted sufficient permissions, an Admin account ensures all necessary integrations are authorized correctly. If your organization chooses to grant more permissions than those listed below, it will not negatively impact the setup.

Note: For unique permission scenarios or specific questions regarding your solution’s architecture, please reach out to your Customer Success Manager (CSM) for personalized assistance.

Standard i-Hub Permission Matrix

Use this table as a checklist when configuring your user roles for i-Hub enablement.

Category	Recommended Configuration
Asset Bank: Asset	Enabled (All permissions)
Asset Bank: Management	Enabled (All permissions)
Brand	Enabled (Read only)
Content Customization	Enabled (Read only)
Custom Links	Enabled (Read only)
Dynamic Asset Transformation	Enabled (Read only)
Homepage	Not required for i-Hub enablement
Preset	Enabled
System Admin	Enabled (Except: “Restore removed assets,” “Restore removed metaproperties,” and “Restore removed metaproperty options”)
Taxonomy	Enabled
Webhooks	Enabled
Reporting	Exporting options not required
Sharing	“Create general asset bank filters” and “View transfer history from others” not required
Users & Permissions	Enabled (Read user profile)
Waiting Room	Not required for i-Hub enablement
CXUC	Not required for i-Hub enablement
Homepage (New)	Not required for i-Hub enablement
Studio	Not required for i-Hub enablement