Team Collaboration

EpicContext is built for teams. This guide covers how members get access, how permissions work, and how to collaborate effectively on your product documentation.

Getting Access

EpicContext uses an invite-only model. Users cannot create accounts on their own.

For New Organizations

If your organization doesn't have EpicContext yet, request a demo from our homepage. We'll set up your organization and get you started.

For Team Members

Organization admins invite new members directly:

1. The admin navigates to organization settings
2. Clicks Invite Member
3. Enters the team member's email address
4. Selects their role
5. Clicks Send Invite

The invited member receives an email with a link to create their account and join the organization.

Roles and Permissions

EpicContext supports role-based access control:

Roles are assigned at the organization level and apply to all projects within that organization.

Collaboration Workflows

Divide and Conquer

Assign different sections to different team members based on expertise:

• Product managers — Product, Users, Metrics sections
• Designers — Brand, Design System, Information Architecture sections
• Engineers — Technical, Development sections
• Strategists — Research, Decisions sections

Review and Complete

Use the block status system to coordinate:

1. Draft — Initial content has been written
2. Complete — Content has been reviewed and approved

The progress dashboard shows completion per section, making it easy to see what still needs attention.

Widget for Stakeholder Feedback

Use the EpicContext Widget to embed context directly in your application. Stakeholders, clients, and team members can:

• Create user stories referencing specific parts of your application
• Leave feedback and comments in context
• See the product documentation that explains design decisions

This bridges the gap between your product context and day-to-day team communication.

Activity Tracking

EpicContext logs all changes with user attribution:

• Who created or updated each block
• When changes were made
• What was changed

View the activity feed on your project dashboard to stay informed about team progress.

Best Practices

• Set a context lead — assign one person to own the overall documentation quality
• Regular reviews — schedule monthly reviews to keep context current
• Start small — don't try to fill everything at once; focus on high-impact sections first
• Use drafts — mark blocks as "draft" until they've been reviewed by the team
• Use the widget — embed context in your application so feedback happens in context, not in separate documents

Next Steps

• Learn about setting up your project
• Set up the Widget for stakeholder feedback
• Explore export formats to share context with your tools