Entity Setup

Entities are the operating boundary for reporting, execution records, access policies, and collaboration.

Step 1: Create the entity record

Start with the core identity of the entity:

• entity name
• entity type
• owner or admin assignment
• basic profile and operating context

Use a stable name and ownership structure from day one because the entity becomes the anchor for reporting, execution history, and follow access.

Company settings

Everything about the company itself is managed under Control › Entity Info (/entities/:id/control/entity). The page has two tabs:

• Public profile — what the Directory shows once the company is published: logo and banner, the business description and tagline, classification (industry, company size, geography), and where to find you (website and social links). The Profile completeness panel on the right measures exactly these fields plus company values and achievements, and each missing field links to the place it is edited. The Directory visibility switch in the same panel publishes or withdraws the listing.
• Company record — the legal facts, private to your workspace: company name, legal entity name, registration number, entity type, the registered address, the people who can act for the company and their confirmation state, and deleting the entity. The public page address (sureshake.com/c/…) is shown here but cannot be changed.

The On this page rail reports each section as Done, n to fill in, or n to fix. Starred fields are expected but never block a save; only what the API refuses does — a blank company name or legal entity name, an entity type change while the entity has child entities, or a website that is not a full https:// address. The save bar at the bottom writes the changed fields on both tabs at once; Discard changes drops them. Image uploads save immediately.

Additional addresses, key personnel, parent entity and organization memberships, and workspace settings (document inbox, feature sections, notifications) are listed under Managed elsewhere and open their own managers.

Step 2: Configure direct operators

Set up the people who actively manage the entity:

• owners
• team members
• internal operators

These users are different from followers. Team access is for operating the entity. Follower access is for viewing selected artifacts.

Step 3: Create organizations when needed

If external access should move with a group instead of a single person, create an organization from the entity detail page.

Organizations are useful for:

• investor firms
• lender teams
• advisory groups
• partner operating teams

After creation, invite users into the organization and wait for them to accept before assuming they inherit any access.

Step 4: Configure follow-access defaults

Before you start sharing reports or execution history, decide how outside principals should gain access.

You can grant access to:

• a single user
• another entity
• an organization

And you can scope that access to:

• all reports
• goals only
• press releases only
• a custom subset of artifacts

Step 5: Run readiness checks

Before generating reports or opening investor workflows, verify:

• ownership is clear
• direct operators are correct
• organization membership is current
• follow-access scopes match real stakeholder needs
• reporting cadence and execution cadence are defined

Validation checklist

• Entity created with correct naming and ownership
• Team operators are assigned and reviewed
• Required organizations are created for grouped access
• Follow-access policy model is defined before external sharing
• Entity is ready for reporting and execution workflows