Client Organisations

Client organisations let your organisation manage other organisations as clients. You can link clients, create briefs for them, control exactly what they see, and give them a portal to review and approve work.

Client relationships

• An organisation can have many clients, and each relationship has a status: active, inactive, or pending.
• You can create a new client organisation or link an existing one.
• Every organisation has a short, human-readable organisation code (for example law-partners) used for linking instead of long identifiers.

Adding a client

Adding a client needs the Manage clients permission (managers, administrators, and owners have it by default). Open Clients in the sidebar, then choose Create New Client:

• Create new: enter a name; an organisation code is suggested automatically (and is editable), along with optional contact details. Runnit creates the organisation and links it as your client.
• Link existing: enter the organisation’s code (such as law-partners).

You can review your clients, change a relationship’s status, or remove a relationship at any time.

Set a client staffing list

The planning pool is open by default, so AI and project planners can initially consider all active staff. To set a smaller default pool:

1. Open Clients and edit the client.
2. Select the Team tab.
3. Choose Set Staffing List.
4. Search by name or email, select the people and user groups AI and planners should consider first, then choose Set Staffing List in the dialog.

The dialog lists the organisation’s groups first, then active staff with each person’s name and email address. When the list is active, listed staff and everyone in a listed group can be used for initial planning and see the client’s projects by default. Organisation administrators and owners keep their organisation-wide access.

Groups on the list appear as chips above the member list, and members who are covered by a group show Via group instead of a Remove button. To take a group off the list, remove its chip; its members keep any direct listing they also have. Changing the group’s membership later changes who is in the pool automatically.

The list doesn’t permanently exclude everyone else. A project owner or project admin can add another active staff member to one project’s Team. That project membership lets the person work on and see that project only. It doesn’t add them to other projects for the client or change the client staffing list.

Use Add to List to expand the default pool. Remove members and groups from the Team tab when they should no longer be considered by default. Removing the final entry (person or group) restores the all-staff planning default.

If the staff list can’t be loaded, choose Try again in the dialog. Runnit doesn’t enable the save action until the list has loaded and you’ve selected at least one person or group.

The staffing list also controls who can see a client-scoped Kanban board. Staff restricted to other clients don’t see the board or its name. See Kanban & Gantt for creating boards.

Client restrictions apply to client work only. A project with no client is an internal project of your own organisation, and everyone who can see projects can see it, whichever clients they’re staffed to. Use project team membership, not the client field, when internal work should stay with a smaller group.

Briefs for clients

Briefs are linked to a client organisation. In the brief builder you pick the client from a dropdown, or create one on the spot, and the brief is associated with them. Client work created this way can also flow into master projects and the client’s brand assets.

Set client planning rules

The client edit page can override your organisation’s AI project planning defaults for that client:

• whether a budget is required, optional, or ignored;
• whether planning prioritises commercial efficiency, a balance of cost and capacity, or timing and capacity;
• whether financials use billable rates, internal cost, chargeback, or stay hidden; and
• whether the default rate card is automatic or needs confirmation.

The client’s AI Directives tab holds that client’s overrides of your organisation-wide AI Directives. Add a project_creation.md file for required roles, task patterns, review rounds, meeting allowances, and exclusions that should apply whenever a brief becomes an AI-created draft project for this client. Files with other names override or add other behaviours, such as copywriting or brief refinement rules. Editing these files requires the Manage AI agents permission.

Client rules override organisation planning defaults. They still cannot bypass permissions or actual capacity. Initial plans use the client staffing list, while an existing project’s explicit team can include a project-only member.

Generate a client’s brand guidelines

Each client has a Brand Guidelines tab holding the brand’s canonical guidelines: tone of voice, identity, and rules the assistant consults before producing work. (This collection was previously named Brand Strategy; default names were renamed automatically, and clients without one now have an empty collection.)

While the collection is empty, the tab shows a Generate Brand Guidelines callout. Choosing it opens a Ru chat that interviews you, saves your uploaded source material into Reference Docs, researches the gaps, and generates the guideline set into the collection. While that chat is underway the callout offers Open Brand Guidelines Chat, returning you to the running conversation rather than starting another. See Assets for the full flow.

Controlling what clients see

Each brief has visibility settings so you decide what a client can and can’t see. By default, sensitive details are hidden:

Detail	Default visibility
Staff names	Hidden
Billable rates	Hidden
Internal notes	Hidden
Team availability	Hidden
Time estimates	Visible

These settings are configurable per brief. Filtering applies automatically to everything a client sees. Internal comments are never visible to clients.

Optional approval workflow

You can require client approval on a brief. When enabled, the brief stays in draft until the client approves it; the client can approve it or send feedback first. Approval is optional and set per brief.

The client portal

Clients get their own portal where they can:

• See every project created for them.
• View project details, with hidden fields removed according to your visibility settings.
• Add comments and feedback.
• Approve a project when approval is required.

Note

Each client only ever sees their own work, and you stay in control of what is shared. This gives clients useful transparency without exposing internal detail.