> ## Documentation Index > Fetch the complete documentation index at: https://help.zarms.cloud/llms.txt > Use this file to discover all available pages before exploring further. # What you can do with ZARMS > ZARMS is a workspace where your team turns each piece of work into a card and shares whose turn it is to act (the ball). Learn the basic ideas: teams, boards, cards, and the ball. ZARMS is a workspace where your team turns each piece of work into a **card** and everyone can see whose turn it is to act. Each card makes it clear who acts next, so you no longer hear "I thought someone else was doing it" or find work stuck waiting for a review. ## Four words that explain it all To use ZARMS, you only need to know four words: team, board, card, and ball. A **team** is the organization that uses ZARMS together, such as a company or group. You invite members, sign up for a plan, and change settings for each team. One person can belong to more than one team. A **board** is a container that groups related cards. You create boards for a department, a project, regular work, and so on. You can see how work is going in Kanban, List, or Timeline view. A **card** is one piece of work. Each card has a status (Draft → Not started → In progress → In review → Done), assignees, and a due date. You put the card's description and files in the Google Doc and Google Drive folder that come with each card. The **ball** tells you who acts next on a card. In ZARMS, the person who needs to act next on a card *has the ball* — it's their turn. The ball moves between assignees as the card's status changes. For example, when a card is In progress, the person doing the work (the Processor) has the ball. When it's In review, the person checking it (the Reviewer) has the ball. Home and My Board collect the cards where you have the ball. ![Diagram showing the ball moving from the Creator to the Processor, the Reviewer, and the Receiver as a card's status moves from Draft to Done](https://mintcdn.com/xgeneinc/N4TaKb3b86sRVhrq/images/ball-flow-en.svg?fit=max\&auto=format\&n=N4TaKb3b86sRVhrq\&q=85\&s=398496ed20070828379fb95808217afd) To learn more about how the ball moves, see [Status and the ball](https://help.zarms.cloud/en/cards/status-and-ball.md). ## What you can do | What you want to do | How to do it in ZARMS | | - | - | | Make sure nothing falls through the cracks | Turn work into cards and add assignees and due dates. You get an email when a due date is near | | Make it clear whose turn it is | When you move a card's status forward, the ball goes to the next person. Cards that are your turn are collected in My Board | | Keep a record of what happened | Comment on a card and mention people to let them know. Changes to the status or due date are also recorded in the comments | | Keep files in one place | Write the description in each card's Google Doc, and put files in its folder | | See how work is going | View a board in Kanban, List, or Timeline view. Use Insights to look back at things like the share of cards done on time and how many days cards waited for review | | Hand off research and tedious updates | Ask AI "What do I need to do this week?" You can also ask AI to create cards or change assignees, after you confirm | | Connect from other tools | Work in ZARMS from AI agents such as Claude, ChatGPT, and Cursor, or through the API | AI, the API, and connections to AI agents (MCP) are available during the trial and on the Starter plan or higher. For details, see [Plans and the trial](https://help.zarms.cloud/en/billing/plans.md). ## What ZARMS doesn't have * **A text editor inside the app**: You write card descriptions in Google Docs. You can use tables and images with Google Docs features as usual. * **Password sign-in**: You can only sign in with a Google account. * **Per-user pricing**: Pricing is a flat fee per team (Basic is free). ## The thinking behind it ZARMS has a few rules that may surprise you: a card has four roles instead of one assignee, cards can't be deleted, and boards can't be private. They all come from a few ideas: remove the places where work gets stuck with simple rules, keep work open, and keep a record of how decisions were made. * The ideas behind ZARMS: [How ZARMS thinks about work](https://help.zarms.cloud/en/concepts/philosophy.md) * Coming from another tool: [How ZARMS differs from typical project management tools](https://help.zarms.cloud/en/concepts/differences.md) * Look up a term: [Glossary](https://help.zarms.cloud/en/concepts/glossary.md) * Tips for writing cards: [Write cards people understand](https://help.zarms.cloud/en/cards/write-good-cards.md) ## What to read next * If you were invited: [Join a team you were invited to](https://help.zarms.cloud/en/getting-started/join-team.md) * If you're setting up ZARMS: [Start using ZARMS in your organization](https://help.zarms.cloud/en/getting-started/create-team.md) * What each part of the screen does: [Find your way around](https://help.zarms.cloud/en/getting-started/screen-tour.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.