Source
Sales content management — found from sitemap — Outreach
Checked for Outreach on 20 Oct 2026
- Page
- https://support.outreach.io/support/solutions/articles/159000425880-outreach-content-governance-overview-and-faq
- Checked
- 20 Oct 2026, 13:55 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:336c7546fe484046c56b3d3d6e3990d09e7c5cbb0c920d2d89b3d669dddbf0ae
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Content governance description Report an error
“Outreach's Content Governance capability allows organizations to restrict access to Sequences, Templates, and Snippets only to users that should be able to see them by placing them into a Collection, and then associating that Collection with a Team of users.”
-
Teams collections relationship Report an error
“One Team can be associated with multiple Collections, and one Collection can be assigned to multiple Teams.”
-
Rbac compatibility Report an error
“Content Governance is a backward-compatible, opt-in feature that admins would need to enable in their organizations before users can use it. It is also fully compatible with the existing Role-Based Access Control (RBAC) settings you have put in place.”
-
Governance without feature sharing Report an error
“If Content Governance is NOT enabled, within content Sharing settings, users can select either Others can only see it or Others can see and use it to provide access to anyone in the organization.”
-
Public collection Report an error
“Any content associated with the Public Collection will be available to everyone in the organization.”
-
Public collection reserved name Report an error
“Note that the Collection name Public (the single word, as typed) is reserved in the Outreach platform as a system-owned Collection name and cannot be changed or deleted by admins or end users.”
-
Content manager role Report an error
“Once enabled, users with Profiles that have only enabled manage collections will be able create, edit, and view all content within collections. However, they will not have permissions to create, edit, and view users within the teams.”
-
Default content manager profile Report an error
“On Outreach instance creation, the default profile for Content Managers provides a pre-cofigured set of permissions that you can provide to content creators and managers inside your organization.”
-
Supported content types Report an error
“Sequences, Templates and Snippets can be added to Collections in this release. Other types can be added through future roadmaps if there’s popular demand.”
-
Feature disable rollback Report an error
“You can disable Content Governance by reversing the options selected on the profiles and content types it was enabled for.”
-
Governance scope per profile Report an error
“Content Governance is enabled per Profile, so individual user's access depends on whether the feature has been enabled for their profile.”
-
Nonadmin permissions requirement Report an error
“Note: Admins will need to provide non-admins with the appropriate Teams and Collection management permissions.”
-
Access enforcement after enablement Report an error
“However, once Content Governance is enabled, access to content within those Collections will be restricted to the user’s Teams memberships only.”
-
Shared content use intent Report an error
“When the User wants to actually use the content, the content owner's original sharing intent is enforced -- that is, Others can only see it vs. Others can see and use it.”
-
Rbac hierarchy model Report an error
“RBAC: General Access Control mechanism used by features across the product to assign, manage, and revoke user access to specific resources and actions allowed on them. Can provide derived access through organizational hierarchy.”
-
Teams collections hierarchy Report an error
“Teams-Collections Access Control: Access Control mechanism designed specifically for Team-based selling motions, and used in conjunction with Collections to create access control islands. Does NOT depend on organizational hierarchy.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The CRM Integrator Sales content management
- The Data Protection Officer Sales content management
- The Enablement Manager Sales content management
- The Head of Sales Sales content management
- The Product Marketer Sales content management
- The Skeptic Sales content management