Clanker CloudClanker Workspace
Give your small team a shared place to finish the work.
Clanker Cloud gives a three-to-five-person business a shared home for source files, reports, operating reviews and reusable Agents. Create an organization for the work your team owns, choose each person’s access and keep reviewed deliverables with their next action. A founder can set the direction, an operations lead can prepare the work, and a colleague can continue from the saved result.
Start with $20 in included credits. See usage and plans.
Give each colleague the access their job needs
An owner or admin invites the colleague’s verified sign-in email from People. The colleague accepts under Organizations using that account and receives the assigned role. An invitation does not make someone an administrator.
Choose roles around the work and the decisions each person should make. Administrative access, building work and managing billing are distinct responsibilities.
| Role | What the role can handle | Decision to make before assigning it |
|---|---|---|
| Owner | Organization ownership and administration. | Who will remain responsible? Only owners change ownership, and at least one owner must remain. |
| Admin | People, shared work and organization data controls. | Who should invite colleagues or manage policy? Promotion does not change Business sponsorship. |
| Billing | Organization billing, alongside owners. | Who should manage organization spending rather than administer everyone’s work? |
| Builder | Building work within the access available to the role. | Who needs to create the team’s working resources? |
| Member or guest | Using the work they have permission to access. | Which reviewed material does this person need for their part of the task? |
Sources: Invitations, roles and ownership · Organization data controls
Separate the Business plan from the team’s working budget
Business is currently $50/month with $200 in monthly subscription credits. The original creator’s active Business subscription is the default sponsor for the organization’s Business features. Adding or promoting an admin does not change that sponsorship.
Organization credits and spending limits are separate from the creator’s personal plan credits. Creating an organization does not copy the monthly allowance, and another colleague’s Business subscription does not automatically replace the creator’s sponsorship. Review the organization’s own balance and billing before starting paid work.
| Cost or account | What it covers | What your team should check |
|---|---|---|
| Each person’s account | Their own plan and personal credits. | An invitation is not a personal subscription upgrade or a transfer of credits. |
| Business sponsorship | The organization’s Business features under the default creator sponsorship. | Confirm the sponsoring subscription stays active when responsibilities change. |
| Organization credits and limits | The separate budget for organization work. | An owner or billing-role colleague reviews the balance and spending settings. |
| An external assistant | That provider’s subscription and its own model use. | Include it alongside applicable Clanker-hosted work and cloud-environment charges. |
Sources: Current plans, credits and usage · Business sponsorship and separate organization credits · Business policy administration
Inspect a weekly review your operator could hand to the owner
The fictional capacity packet provides a small, checkable operating review. After existing commitments and unavailable time, delivery has 4 hours, design has 4 and operations has 8. Incoming requests leave a 2-hour delivery gap and a 6-hour design gap; the operations request fits with 4 hours remaining. The roles’ hours are not interchangeable.
Open the editable workbook and planning brief beside the source rows. The brief gives the review owner options to consider before committing work: sequencing, reduced scope or revised estimates. It keeps dates, assignments and overtime unapproved. These are authored fictional reference files, not a recorded team run or customer outcome.
Sources: Inspect the review workbook · Read the owner-decision brief · Check the source capacity · Check the proposed requests · Try the complete fictional starter
Leave the next person a result they can act on
For your own review, the operations lead can save the workbook and brief in the intended organization Project, check their figures and attach the exact reviewed file version to a Planner task. Name the review owner, explain the open decision and state the next action.
The colleague needs their own access to the work. They can open the reviewed file, check its sources and prepare the next revision or decision. Reuse an Operations Analyst for the calculation method while each cycle supplies current facts. Planner assignment records the intended role; starting work or configuring a recurring run is a separate choice.
Sources: Keep ownership and reviewed versions with the task · Adapt the Operations Analyst role · Invitations, roles and ownership
Review the handoff when someone’s responsibilities change
Before a colleague leaves a process, keep the current sources, reviewed file and next action available in the intended organization Project. Have the appropriate owner or admin review ownership, membership, sharing and any connections or recurring work that the process uses.
Separately confirm subscription sponsorship and organization billing with the responsible administrator or support. A changed role or task assignee does not establish that billing moved. Review personal work separately rather than assuming it becomes organization work or transfers automatically.
Sources: Invitations, roles and ownership · Business sponsorship and separate organization credits · Review sharing, connections and retention
Common questions.
When should a small team choose Clanker Cloud?
Choose Clanker when a founder, operator and colleagues need continuing source context, saved deliverables and a clear handoff. A weekly operating review or client update is a useful first task. An individual’s one-off answer may already fit their current assistant.
Who creates the organization and owns the shared work?
Any account can create an ordinary organization after verifying its sign-in email. The creator becomes an owner with administrator access. Work created in the organization belongs to the organization; personal Workspace work stays separate. Keep the intended organization context explicit.
How does a colleague join the team?
An owner or admin invites their verified sign-in email from People. They accept under Organizations with that account and receive the assigned role. Joining does not make them an admin or grant access to every resource; choose the role and work access they need.
Does every colleague need their own Business subscription to join?
Free, Lite, Pro and other account tiers can join an ordinary organization by invitation. Membership and personal subscriptions are separate. The original creator’s active Business subscription is the default sponsor for organization Business features; organization credits and spending limits still require their own review.
Can we spend the creator’s monthly credits as organization credits?
Creating an organization does not copy the creator’s personal monthly subscription credits into its balance. Organization credits and spending limits are separate. Check the organization’s own available credits and billing; do not assume that a colleague’s allowance is pooled into the team budget.
Does making an operations lead an admin change who sponsors Business features?
No. Adding or promoting an admin does not change the default creator sponsorship. Owners and billing-role members manage organization billing; administrators manage people, shared work and data controls. Review sponsorship and billing separately when responsibilities change.
Can a colleague continue from an operator’s saved review?
Give the intended colleague access to the organization work, keep the current source packet in its Project and attach the reviewed deliverable version to the task. Include the open question and next action. The colleague checks the saved work before continuing; assignment alone does not start execution.
What should we review when someone leaves the team?
Review the ownership and access needed to keep the process working, including its source files, reviewed deliverables, sharing, connections and recurring work. Separately confirm subscription sponsorship and organization billing with the responsible administrator or support. Do not assume that changing a role transfers personal files, credits or billing.
Are ZDR, data residency and encryption available for our team?
ZDR, data residency and encryption are coming soon. Evaluate the current service using its published terms and the business material you are permitted to supply. An organization or Business subscription does not activate these planned controls, and external providers retain their own data policies.
Sources: Explore Clanker Workspace · Creating an organization · Invitations, roles and ownership · Business sponsorship and separate organization credits · Current plans, credits and usage · Current and planned data controls
Content reviewed against the Workspace Guide & FAQ. Features and access can depend on your account.