Sistava is an AI workforce platform where solo founders hire AI employees to run their business around the clock. Each AI employee has a specific role like sales, marketing, or customer support, with real tool integrations, persistent memory, and the ability to work inside your existing apps like Slack, Gmail, and HubSpot.

What is an AI employee?

An AI employee is an autonomous AI agent with a defined role, persona, skill set, and tool access. Unlike a chatbot that only answers questions, an AI employee takes on recurring work like writing emails, qualifying leads, answering support tickets, and publishing content, and it works on its own around the clock without being prompted each time.

How is Sistava different from project management software?

Sistava is not project management software. You hire AI employees who do the work, not a tool that tracks work done by humans. Your AI employees run sales outreach, write marketing content, answer support tickets, and handle operations on their own, without constant supervision.

How much does Sistava cost?

Sistava has a free plan you can start without a credit card, plus paid plans that scale with how much work you hand to your AI employees. See the pricing page for current plans.

What can AI employees do on Sistava?

Your AI employees take on the recurring work that runs a business: qualifying and reaching out to leads, writing and publishing marketing content, answering support tickets, and handling day to day operations. Each one comes with a role and skill set, so it can start working the day you hire it.

Sistava is built for solo founders and small teams who need to run sales, marketing, support, and operations without hiring a full human team. It gives you the equivalent of a growth team you can hire in minutes.

Collaborate Across Workspaces

Bring people into the right workspace, give them the right operational access, and share only the specific resources that need to cross a workspace boundary.

TL;DR

Workspaces keep teams and data separate by default. Invite people as Owners, Admins, or Members, then use custom operational access when a role needs one exception. Share a supported resource separately when it must cross workspace boundaries.

How Collaboration Works

There are three separate layers. Keep them separate when deciding what someone needs.

Layer	Controls	Example
Workspace membership	Whether someone works in this workspace	Invite a colleague to join your company workspace.
Role and custom access	What a member can administer	Let an operations lead invite people without making them an Owner.
Resource Access	Who can open one file, document, CRM record, task, Project, Sprint, calendar meeting, or email	Share one sensitive report or customer record with a partner.

Joining a workspace does not merge another workspace's employees, chat history, training, billing, or settings. A direct share does not make its recipient a workspace member.

Invite Your Team

Only an Owner or Admin sees Settings > Organizations and can invite people; a Member does not get this section.

Open Settings > Organizations > Members.
Enter the person's existing Sistava account email.
Choose their role. An Owner can invite as Owner, Admin, or Member; an Admin can only invite as Member.
If you are an Owner, you can also set custom access exceptions for that person before sending. Then send the invite.
The person accepts the invitation and sees the workspace in their workspace switcher.

The invite form shows how many seats are left on the plan and blocks sending once the workspace is full. Pending invitations sit in a list below the form so you can see who has not accepted yet.

An invitation is not workspace access. Until the invited Sistava account accepts it, that person cannot open the workspace, use its roles, or see its data. You can cancel or change a pending invitation before it is accepted.

Use a separate workspace for a different business, client, or billing boundary. Invite people into the workspace where they need to collaborate instead of sharing every resource one by one.

Choose a Role

What a person can do	Owner	Admin	Member
Work with ordinary workspace resources	Yes	Yes	Yes
View team members	Yes	Yes	No
Invite new members	Yes	Yes, as Member only	No
Manage non-Owner members	Yes	Yes	No
Manage supported resource access	Yes	Yes	No
Manage billing, settings, or deletion	Yes	No	No
Grant Owner or Admin access	Yes	No	No

Start most internal teammates as Members. Use Admin for a trusted person who runs people and access but does not own billing or workspace survival. Keep Owner for the accountable operator. Every workspace must retain at least one Owner; the app blocks demoting or removing the last one.

Custom Operational Access

An Owner can open a non-Owner member's Actions menu and choose Customize access. They can turn these operational capabilities on or off without changing the person's role:

View team members
Invite new members
Manage non-Owner members
Manage resource access

Billing, workspace settings, deletion, and assigning Owner or Admin status always remain Owner-only, even with custom access turned on. A member who needs more access should ask an Owner to update their role or custom access, or use Request access review on the Roles page to ask directly.

Resource Access currently supports Drive files, Drive documents, CRM contacts, companies, deals, Content items, tasks, Projects, Sprints, calendar meetings, and mailbox emails. They are private from the public web.

Access choice	Who receives it	Result
Workspace default	Accepted members of the source workspace	Normal internal collaboration.
Restricted	The policy owner, admins, and named people	Sensitive item stays limited.
Direct share	One existing Sistava account	Recipient receives a protected in-app offer for that item only.
Public link	Nobody	Public anonymous links are not available.

Open the item in Drive, Company > CRM, Content, the Tasks drawer, Manage projects, Sprints, or a meeting card in Calendar, then click Share. You can share a single CRM contact from its drawer, or select several CRM rows and use Share selected. Control Access & Share Resources explains roles, links, and revocation in detail.

For compatible internal resources, choose Can view & comment for normal review or Can edit & delete when the person must change the item. Read-only is used only where that entity supports no commenting or editing. Drive's current Editor permission includes recoverable deletion; Task Editor access currently also includes permanent deletion behind a server permission check. A separate delete permission is planned before sensitive-work sharing expands further.

Projects are the exception: they have no comments yet, so choose Read-only or Can edit & archive. Sharing a Project controls the Project's name, purpose, and lifecycle. It does not automatically share every task or Drive file grouped under it; each item keeps its own access decision.

Calendar meetings also have no comment thread. Choose Read-only to reveal only safe appointment details, or Can edit, move & cancel for an internal recipient who must manage a meeting booked in Sistava. Meeting links and organizer details stay hidden from Viewers. A meeting from Google Calendar, Outlook, or another connected calendar remains controlled by that source.

CRM companies and deals are also Read-only shares today: their human screens have no comment or direct edit action to grant. Sharing a deal never automatically shares its linked company or contact; those names and links stay hidden until the recipient separately has access to that record.

Assigning a restricted task does not automatically share it. First give the assignee Can edit & delete access in the Task drawer; then assign the task. This keeps its task notification and deep link private too.

Move a Selected Copy to Another Workspace

If you own more than one workspace, share a compatible supported resource to your own Sistava account. Switch to the destination workspace, open the in-app share notification, and choose Add private copy.

Nothing is added until that action. The destination gets a new private file, document, or CRM contact rather than the source record. CRM companies/deals, Content items, tasks, Projects, Sprints, calendar meetings, and mailbox emails are view-only shared work: they do not offer Add private copy. Revoking the original share blocks future imports but does not delete an already accepted copy.

Good to Know

Chat uploads, training uploads, email templates, and posts do not yet have their own per-item Resource Access control.
Sharing a link never grants access by itself. The recipient must sign in and pass the item's access check.
Direct recipients outside the source workspace have read-only access to the protected offer: they cannot comment or edit, do not become workspace members, and cannot see other source resources.
A directly shared calendar meeting exposes only its time, status, and assigned employee. It never exposes the meeting link, organizer, or source mailbox.
A locked Private notebook in Drive belongs to the person whose conversation created it. They can approve a teammate's read-only request; Owners and Admins do not automatically read it, and approval never makes the notes part of the employee's conversation with someone else.
Resource Access controls the human workspace/API surface and the scoped private-notebook flow above. It does not yet cover every AI employee CRM context, connected tool, training source, or autonomous action; those separate access boundaries are still being designed.
The current notification for a direct share is in-app. Email delivery for resource shares is not enabled.

Frequently Asked Questions

Q: Should I invite a partner or share a file with them? A: Invite them when they need to collaborate throughout one workspace. Share a supported resource when they need only that selected item.

Q: Can one person have different access in different workspaces? A: Yes. Roles and custom operational access belong to each workspace membership, so the same account can be an Owner in one workspace and a Member in another.

Q: Does sending an invitation give someone access immediately? A: No. The invitation only asks the named Sistava account to join. Access starts after that account accepts the invitation, and a pending invitation can be cancelled or changed first.

Q: Can I make a file public? A: No. Public anonymous links are not available, so files and contacts are never exposed to the web by Resource Access.

Q: What happens when I remove a direct share? A: The recipient loses the protected source view and cannot import it later. A private copy they already accepted remains in their destination workspace.