Enterprise access
Agreed access to EBD resources and learning for a defined group of users.
- Confirm the audience and number of users
- Agree resource and learning access
- Define permitted internal use
- Set onboarding and support expectations
The enterprise knowledge system
For teams and organizations
A shared language.
A stronger capability.
Discuss access, learning, and practical resources around the work your team needs to do.
Two distinct ways to work with EBD
Team access is not an advisory engagement.
Advisory
A separately scoped engagement for an organization-specific problem.
- Define the problem and intended outcome
- Agree the required inputs
- Specify work products and exclusions
- Confirm timing, availability, and fees
Start with the capability
Tell us what your team needs.
Who will use EBD—and what work do they do?
What decisions or capabilities need to improve?
Which resources, learning experiences, or support would help?
What timing and internal-use requirements matter?
Agreed scope, not assumptions
Enterprise details.
How is enterprise access priced?
Access and pricing are agreed around the organization’s scope and requirements. No standard offer on this page establishes seat pricing or minimum commitments.
Are SSO, reporting, and automated seat management included?
SSO, reporting, and automated seat management are not assumed to be included. Requirements and actual platform support must be confirmed in the agreed scope.
Can we combine team learning and advisory?
They can be discussed together, but access rights and advisory deliverables need separate, explicit scope.