Give your team one shared plan

Tidigar Business · Paid

Keep a launch in a Business organisation so colleagues work on the same plan. Invite the people who need access, choose who may edit and decide how the organisation's plans can be shared outside it.

Bring a launch into your organisation

Use this small launch to try the workflow. The frame is an interactive demonstration of the plan, without a real team or Business membership. Choose Open in Tidigar to open your own copy; inviting people requires a Business organisation.

1. Open Properties → Move to… and choose your Business organisation. If you do not have one, create it in the browser and set up its subscription when asked. See Library and storage for that first move.
2. Open your account menu, then your organisation under Organisations. Check its name and your role before changing anything. The same account can belong to several organisations, with a different role in each.
3. As an owner or coordinator, choose Invite People, enter a colleague's sign-in email and select Editor. Choose Invite. Invite someone as Viewer when they should read the launch without changing the shared plan.
4. Ask each colleague to open the invitation email, sign in with the invited address and choose Accept in the account sheet. Opening the email link alone does not join the organisation.
5. Open the launch and choose Share → Copy link to plan. Send this address to the members who accepted. An editor with plan editing access can update Prepare the release; a viewer can read the shared result.

Each organisation has its own plans, members and settings. Joining one does not upload a colleague's local plans or give that organisation access to plans they keep elsewhere.

If you started in Personal, the first invitation asks you to name the organisation. Naming it turns that existing space into an ordinary organisation, keeping its plans and subscription. You do not need to move the launch again.

Choose the smallest role that fits

To make a colleague a coordinator or owner, invite them as an editor or viewer first. After they accept, an owner opens their member row and changes Role. Role changes apply immediately; there is no second acceptance step.

Owners, coordinators and editors count as paid seats; viewers do not. Business subscriptions have a minimum of three paid seats. The invitation sheet explains whether another editor fits the existing subscription or adds a seat when they accept. A role allows editing only while the organisation is writable; an expired subscription can make an owner's plan read only too.

Before handing over ownership, promote another member to Owner and check that the change succeeded. Tidigar refuses to remove or demote the last owner, including when that person tries to leave.

Protect the launch while colleagues read it

When the release dates are agreed, protect the launch so the team can read it while its owner and chosen editors maintain it. In the browser library, open Access on the launch's plan card.

1. Under General access, choose Protected. Everyone in the organisation can still read it. The plan owner, invited editors and organisation owners can change it.
2. Under People, choose Can edit for the colleague maintaining the dates. The person must already be a member of the organisation. Can view keeps their access read only on this protected plan; Not invited removes the plan invitation. An organisation viewer stays read only even with Can edit.
3. To hand the launch over, choose its new Plan owner and confirm Transfer ownership. Check your own invitation before transferring: you may lose editing and access management rights.
4. To let all editors work on it again, choose Open.

An organisation owner can choose New plans → Protected on the organisation's page. It applies only to plans created afterwards, including plans moved or copied into the organisation; existing plans keep their level. The starting default is Open. Private plans are not available yet.

The plan owner and organisation owners and coordinators manage access. Coordinators need ownership or an editing invitation to change protected content, even though they can manage access. Organisation owners can change every plan. The organisation's role and write entitlement still apply.

Opening a protected plan without editing rights lets you explore it locally; those edits do not update the shared plan. Rights refresh with the plan list. Waiting edits can be sent if you later gain editing rights, so check your local changes before continuing. Assistants and CLI tokens follow the same plan rights.

A plan invitation is separate from the organisation's email invitations: it chooses a current member's rights on this plan and does not invite a new member. If a member leaves or is removed, their plans pass to a remaining organisation owner and their plan invitations are removed. Copies, files, Markdown and share links do not carry these access settings. Screens and embeds retain their own link access; protection controls changes to the shared plan.

Decide what can leave the organisation

An owner opens the organisation's Sharing settings. These switches have different effects:

• Keep plans in the organisation blocks moving plans out, sending copy links and exporting CSV. It also ends existing screen links and prevents new ones. Pictures and printing still work.
• Show previews of plan links lets chat apps show a plan's name and picture to anyone holding its link. It is off by default. A preview never grants access to the shared plan. While plans are kept inside the organisation, previews are unavailable.
• Allow agent access (MCP and CLI) lets members connect assistants and create agent tokens within their access. Turning it off asks for confirmation, revokes every existing token and assistant connection in that organisation and prevents new ones.

For example, keep the launch inside the organisation when the team should continue working from its shared source. Members can still send its member link to each other. Use Sharing a plan for an independent copy where permitted, or Screen links for an updating view without reader accounts.

Let your company's Microsoft accounts join

If your company uses Microsoft Entra, an owner can connect the organisation to the company's Microsoft tenant. Colleagues then join as viewers the first time they sign in with Microsoft, without an invitation each. Viewers take no paid seat; you make editors of those who need to change plans.

1. As an owner, open the organisation and choose Connect Microsoft tenant under Microsoft Entra. Copy the link and send it to your Entra admin. It works once, for seven days; Make a new link replaces it.
2. The Entra admin opens the link, signs in to Microsoft and grants consent on behalf of the organisation. A page then confirms that your organisation is connected, and the organisation's page shows the tenant.
3. In the Microsoft Entra admin center, the admin opens Enterprise applications → Tidigar → Properties, sets Assignment required? to Yes and saves. Under Users and groups, they assign the people or groups who should use Tidigar. Only assigned people can sign in to Tidigar with their work account.
4. Colleagues choose Continue with Microsoft when they sign in. Each joins as a viewer. A viewer who needs to edit finds the organisation's owners and coordinators with their addresses on its page and asks one of them; the owner or coordinator opens that member and changes Role to Editor.

To stop new people joining, an owner chooses Disconnect tenant. Everyone who already joined stays a member until an owner removes them.

Let your company sign in with Okta

If your company uses Okta, or another identity provider with OpenID Connect, an owner can connect it under Company sign-in on the organisation's page. Colleagues then sign in from the Tidigar tile in Okta, or at the organisation's sign-in address, and join as viewers. Your Okta admin needs to make the application; Tidigar keeps no password or secret from it.

1. As an owner, open the organisation. Company sign-in lists three addresses with Copy next to each: Redirect URI, Sign-in address and Public key URL.
2. In the Okta Admin Console, the admin chooses Applications → Applications → Create App Integration, then OIDC - OpenID Connect and Web Application. They enter the Redirect URI as the sign-in redirect URI and the Sign-in address as the initiate login URI, keep Authorization Code as the grant type and leave Require PKCE on.
3. Under Client Credentials, they set Client authentication to Public key / Private key, choose Use a URL to fetch keys dynamically and enter the Public key URL.
4. Under Assignments, they assign the people or groups who should use Tidigar.
5. Back in Tidigar, enter the issuer, your Okta address such as https://yourcompany.okta.com, and the application's Client ID, then choose Save.
6. Choose Sign in to connect and sign in with your own Okta account. Company sign-in is then connected, and your Okta account becomes one of your ways in.

The first time a colleague signs in, Tidigar sends the usual sign-in email to confirm the address. After that they sign straight in and join as viewers; the owner or coordinator makes editors of those who need one. To stop people signing in this way, an owner chooses Disconnect provider. Members stay until an owner removes them.

How teams and access work in detail

An invitation belongs to an email address

Only the account signed in with the invited email can see and accept the invitation. If it is missing, check the signed-in address and organisation name first. A forwarded email or a plan link does not give another account membership.

Invitations expire after seven days. Owners and coordinators can use Resend beside a pending invitation; resending replaces the previous invitation and starts a new seven-day period. They can also revoke it. A recipient can decline it. An accepted, expired, declined or revoked invitation cannot be used again.

An invitation never silently changes an existing member's role. An owner changes that role from the member's page instead. If sending fails, correct the address or reported delivery problem and try again; a message on screen is not proof that the colleague has joined. Pending invitations and member controls need a connection.

Membership covers the organisation's plans

A Business plan link identifies the plan; the recipient's signed-in membership decides access. A non-member is asked to request an invitation or use another account. Membership gives reading access to open and protected plans. A protected plan also needs plan ownership or an editing invitation to change it, except for organisation owners.

A viewer's edits made during local exploration do not write to the shared plan. An editor or coordinator with plan editing access can edit without controlling the organisation's sharing settings. When you need someone to invite colleagues but not change owners or settings, use Coordinator.

Removing someone stops subsequent access checks from authorising them. It cannot withdraw content they have already read or copies they have already made. An offline device learns about membership changes when it reconnects; removing a member does not remotely erase a disconnected device at that instant.

Keeping plans is a workflow rule

Keep plans in the organisation starts off. When enabled, it applies to owners too for moving plans, sending copy links and CSV. Members cannot bypass it by filtering a view, moving to another organisation or letting the subscription lapse. An owner can change the setting, and the owner's Advanced → Download organisation package remains available.

Members can continue working on cached plans offline within their access. Signing out, leaving or losing membership deletes those kept copies when Tidigar processes the change. Before a voluntary sign-out or departure, Tidigar tries to send waiting edits and asks before discarding edits it cannot send. If membership is removed elsewhere, unsent edits in kept plans can be lost when the device learns that access ended. Reconnect and let changes reach Business before a planned handover.

The setting leaves pictures and printing available and cannot recall earlier exports. Treat it as control over the supported sharing and moving workflows. Turning it off allows those workflows again but does not restore screen links that it ended; create new screens if needed.

Previews reveal the name and picture

With previews enabled, anyone holding the member link can obtain the plan's preview, including people outside the organisation. The plan still needs membership to open. Leave previews off when even the launch's name or picture should stay within the team.

Preview responses can be cached for up to a minute, so turning the setting off does not remove every preview immediately. A chat app may keep a picture it already fetched. Keeping plans inside the organisation suppresses previews even if they were previously enabled; check the preview setting again before allowing plans out.

Agent access is a separate choice

Allowing agents does not make plans public or give an assistant a role of its own. Access uses the authorising member's permissions and is limited to that organisation. Turning agent access off affects all its members' tokens and connected assistants, including owners'. Turning it back on permits new connections; it does not restore revoked credentials.

For connecting an assistant or CLI, continue with Use Tidigar Business with an agent. Keep plan sharing and agent access as separate decisions: allowing agents does not turn off the rule that keeps plans inside the organisation.

A connected tenant adds editors, not owners

Only an Entra admin's consent connects a tenant; an owner's link alone, or an ordinary colleague's sign-in, does not. A tenant connects to one Business organisation, and an organisation to one tenant. A second organisation trying to connect the same tenant is refused.

Tidigar reads no users or groups from the tenant. Choose who may sign in with assignment in Entra: without Assignment required?, everyone in the tenant who signs in with Microsoft joins. Blocking or unassigning someone in Entra stops their next Microsoft sign-in, but they keep their seat, and any other way they sign in, until an owner removes them in Tidigar.

People join as viewers, so connecting a tenant never adds paid seats by itself. Only an owner or coordinator making someone an editor does, and that raises the subscription if the seats are full. Coordinators move members between viewer and editor; other role changes stay with owners. Someone an owner removed, or who left, is not added again by signing in; invite them to bring them back.

A colleague whose address is on a domain the tenant has verified gets an account at once. Otherwise, including guests, and whenever an account with that address already exists, Tidigar first sends the usual sign-in email to confirm the address, and the person joins after confirming it.

Company sign-in confirms each address once

Okta and other providers do not prove that an address belongs to the person, so a new colleague always confirms theirs by email once. A provider connects to one Business organisation; another organisation trying to use it is refused. As with Entra, choose who may sign in with assignment at the provider; someone you unassign keeps their seat until an owner removes them in Tidigar.

Leave, hand over or delete

Use Leave organisation when you should lose access while the team continues. An owner can remove another member from their member page. Check waiting edits first and arrange another owner before the last owner leaves.

Advanced → Delete organisation… is a different action: an owner confirms its name, its subscription is cancelled and its plans, memberships, invitations and agent access are deleted. This is immediate deletion of the organisation, rather than moving a plan to the 30-day trash. Consider Download organisation package before deleting it. If cancelling the subscription cannot be completed, deletion stops and reports the problem.

In the apps you can open Business plans and use the available account controls. Create organisations and manage subscriptions in the browser. Local app documents, external files and calendars keep their own storage rules; see Library and storage.