Organizations & Follow Access
Create organizations, invite members, and control which principals can follow entity reports.
Sureshake now separates three related concepts:
- Entity team access controls who operates the entity directly.
- Organization membership groups external or internal collaborators under one managed principal.
- Follow access controls what a user, entity, or organization can continuously see.
Use organizations when you want access to move with an accepted member list instead of managing every follower one by one.
Create an organization
Entity owners can create organizations from the entity detail page.
Common examples:
- investor firms
- lender teams
- advisors
- board observer groups
When you create an organization, you become its initial active owner.
Invite and manage members
Enter the organization name and optional type or description.
Search for users by name, email, or company and assign a role before sending the invitation.
Pending invitations do not grant inherited access. Access begins only after the user accepts.
Owners and admins can update member roles or revoke membership when access should stop.
Invitation workflow
Invited users can review organization invitations from the shared invitations workspace at /team-invitations.
They can:
- accept the invitation
- decline the invitation
- review the organization name, type, and inviter before deciding
Accepting an organization invitation activates inherited follow access immediately. Declining or remaining pending does not.
Grant follow access
Entity owners can grant follow access to three principal types:
- User: one specific person
- Entity: the entity owner plus accepted current team members
- Organization: accepted active organization members
This is configured from the entity followers section.
Access policy modes
When granting follow access, choose the smallest scope that matches the recipient's need:
- All reports: continuous access to the full report set for the entity
- Goals only: access to artifacts tagged for goal and execution workflows
- Press releases only: access limited to press-release style artifacts
- Custom: choose explicit report types, document source types, tags, or specific reports
Linked artifact access
Follow policies also control how linked artifacts behave:
- None: no linked artifact access
- Derived only: followers can see execution-facing summaries or derived evidence, but not the entire linked artifact
- Full artifact: followers can open the underlying artifact when it matches policy
Derived only is the safest default for investor and diligence workflows.
Recommended operating model
- Use user principals for one-off diligence or advisor access.
- Use organization principals when membership changes often and you want access to follow accepted members automatically.
- Use entity principals when another company should inherit access through its owner and active team.
- Start with a narrow policy, then expand only if the audience needs more context.
Revocation
Access can stop in two ways:
- revoke the follow policy from the entity
- revoke or lose the underlying organization or entity membership that supplied inherited access
Both paths should be part of your routine access review.