Use the apps in your Sasha, understand who can reach them, and know what each bundled app does today
Apps are small applications inside Sasha that keep their own records. Open them from Agents that work for me in the side menu, use them from Claude, and know their limits.
- Where
- The Agents that work for me section at the top of the side menu, above the projects. Business apps and roles come first, starter apps under Examples. Click an app name to open it in a panel on the right.
- Who
- Admin and staff accounts that existed when an app was first added get manage access to it. Everyone else needs a grant, and today no screen gives one.
- Needs
- A separate sandbox web address for apps, set by whoever runs your Sasha. Without a valid one, Sasha does not start.
What it is
An app is a small application inside Sasha, for work that needs a form or a table instead of a chat. An app can keep its own records in its own database, apart from your documents. Some records are shared by everyone who uses the app. Others belong to the person who made them.
This page goes deeper than the help article Use and manage apps built on your knowledge. It covers the two apps that ship with Sasha, how access works, how apps are kept safe, and what does not work yet. For the Finance Agent and the Marketing Agent, see Add a Finance Agent or a Marketing Agent, read its report, and keep its brief right.
The Agents that work for me section of the side menu
The side menu shows Agents that work for me above Projects. Click Agents that work for me to open or close the list. Hover over an app to see its description. The list has four parts:
- Your business apps and your team roles, such as a Finance Agent, in name order.
- For an admin only: each role that is not added yet, with Set up next to its name. Click it to see what it does, Questions it answers and What it needs. Set it up puts "Set up our Finance Agent." (or the role's name) into the chat box. Press Send, and Sasha sets it up with you (Add a Finance Agent or a Marketing Agent, read its report, and keep its brief right). If the roles cannot load, the list says "Roles could not load."
- For an admin only: New agent. It puts "I want a new agent." into the chat box. Press Send, and Sasha lists the agents it can set up and asks which job you want done.
- Examples: starter apps that show what an app can do, such as Time Sheet Entry. Copy one to make your own.

For staff, the whole section is hidden when you have no access to any app. It is also hidden when Sasha cannot load the list.
Open an app
- Click the app name under Agents that work for me.
- Sasha switches to the chat tab and opens a panel on the right. On a phone, the panel fills the screen.
- The panel header shows App, the app name and an X to close it.
- With a project open, the chat sits beside the app; drag the edge between them to change the widths. With no project open, the app fills the space and its header shows Chat beside this app. Click it, type a project name and choose the project: the chat opens beside the app.
Messages you can see in the panel:
| Message | What it means |
|---|---|
| "Loading app…" | Sasha is fetching the app. |
| "This app is unavailable. Try opening it again." | Sasha could not load the app. Try again. If it persists, the sandbox address of your Sasha can be wrong. |
| "An app is already open. Close it before opening another." | Only one app can be open at a time. |
Edit raw data
A person with manage access to an app that keeps records sees ⋯ in the panel header. Edit raw data in that menu opens the Raw data view. The same view opens by itself when the app page fails to start.
The view says: "For when the app will not load. Changes here skip the app's own checks, so use the app itself when you can."
- Click a table name to see its records. Choose a table to recover. shows until you choose one.
- New, Edit, Save and Cancel change a record. Load more shows more rows. Reload reads them again.
- If someone else changed the record after you loaded it, the view says "This record changed since you loaded it."
- Back to app returns to the app.
The Raw data view cannot delete a record.
The bundled app
Sasha ships with one app, Time Sheet Entry. Sasha copies it in when it starts. If someone changes it, your Sasha keeps that version, and later updates do not replace it. It shows under Examples.
If your business does not use it, ask whoever runs your Sasha to remove it. They remove it and mark it as removed, so that later updates do not add it back. To bring it back, they remove the mark and restart Sasha.
The Finance Agent and the Marketing Agent are not bundled apps. Sasha builds each one for your business when an admin sets it up (Add a Finance Agent or a Marketing Agent, read its report, and keep its brief right).
Time Sheet Entry
Records hours against projects, one week at a time.
| Part of the screen | What it does |
|---|---|
| New time entry | Date, Project, Hours and Description, then Add Entry. |
| Add a project | Project code and Project name, then Add Project. Shown only while the app has no project. |
| Week heading | Shows "Week of" and the first and last dates of the week. |
| Entries table | Date, Project, Description, Hours and Action. Change the hours in a row and click Save. |
| Total hours | The week's total, and a total for each project. |
- Your entries are yours. Other people cannot see them. Projects are shared.
- Description is optional.
Who can use an app
Each person has one of two levels for each app:
| Level | What the person can do |
|---|---|
| use | Open the app and work with its records. |
| manage | Also use Edit raw data, and (admin or staff only) change the app itself. |
- When Sasha first finds an app, it gives manage to every admin and staff account that exists at that moment. This happens once for each app.
- A person added later, and every member, gets no access until an admin or staff user grants use or manage.
- Today there is no screen for granting access. To grant access, ask whoever runs your Sasha.
- Members cannot sign in to the Sasha web interface, so a member can never use an app's own screen. A member with access works with the app's records only from Claude (Add people to Sasha, give each person a role, and control what members can reach, Who can do what in Sasha).
- Sasha reads access on every request. A removed grant stops working at once.
How apps are kept safe
- A separate web address. An app runs in a frame on a different host name from the Sasha web interface. It cannot read your Studio cookies, your session or the Studio page.
- No network. The sandbox blocks all network calls, and camera, microphone and clipboard access. An app reaches Sasha only through a fixed set of operations: read and change its own records, run its declared actions, ask the chat, and upload files.
- Checks on the server. Sasha checks your access to the app on each operation. Records that belong to one person are kept to that person by the server, not by the app.
- A record of every change. Sasha records each change to an app's records, with the values before and after. A repeated click does not save a record twice.
- No leaks in errors. A missing app, an app you cannot use and a bad request all get the same answer, so the server does not show which apps exist. Error messages come from a fixed list.
The sandbox address is set by whoever runs your Sasha. In production it must be a different host name from the Sasha web interface, or Sasha does not start.
Using apps from Claude
After you connect Claude to Sasha (What Claude can do with Sasha), Claude sees only the apps you can use. Claude can:
- open an app's page;
- list, read and total an app's records;
- create, change and delete records, for an app that allows changes;
- run the actions an app offers, such as the total of your own hours for a week in Time Sheet Entry.
Before Claude changes a record, Sasha asks you to accept the change in Claude. If your Claude cannot show that request, Sasha refuses the change.
An app page opened from Claude shows, but its own buttons cannot reach its records, the chat or uploads. Time Sheet Entry then tells you to use it in the Sasha web interface. Ask Claude to read or change the records instead.
Changing an app with Sasha
Admin and staff users with manage access can ask Sasha, in a chat in the Sasha web interface, to change an app. Sasha follows its app-builder skill: it reads the app's files, makes the change, and checks the app after each step. They can also ask Claude to change an app's files, when Claude is connected to Sasha.
- A change goes live as soon as the app passes its checks. There is no draft, no preview and no undo.
- Apps are plain text files: at most 64 files, 1 MiB (about 1 MB) each.
- If you change a bundled app, updates of Sasha stop replacing it.
- The editing tools change apps that already exist. To add a new app, ask whoever runs your Sasha.
Limits to know
- No screen grants access. Admin or staff accounts added after an app was first found see no Agents that work for me section until someone grants access. The side menu gives no hint why. Ask whoever runs your Sasha.
- Members never see an app's screen. A member with access works with the records only from Claude.
- Studio chat asks before each change. When the AI in a Sasha web interface chat wants to change app records, a box headed Sasha asks opens in the chat with the app's name. It asks a plain question, names who or what it touches, and has two buttons that say what they do, for example Not now and Yes, do it. Sasha makes the change only after you press the button that says yes; Not now stops it. A change that removes data also says "This removes data. It cannot be undone." Inside a team role's page, an admin change opens a Confirm dialog in the Studio window (Add a Finance Agent or a Marketing Agent, read its report, and keep its brief right).
- One app at a time. Opening an app always switches to the chat tab.
- Edit raw data cannot delete. It can view, add and change records only, and it skips the app's own checks.
- Time Sheet Entry. After the first project, the app has no form to add another one; ask Claude to add it. You cannot delete an entry in the app. The week is worked out in UTC, so near midnight in other time zones the wrong week can show.
- Uploads from any app are limited to 10 files and 25 MiB (about 26 MB) in total.
Questions
Why is there no Agents that work for me section in my side menu?
For staff, the section appears only when you have access to at least one app. An admin always sees it. Admin and staff accounts that existed when an app was first added get access automatically. A person added later gets nothing until someone grants access. Today there is no screen for this, and the side menu shows no hint. Ask whoever runs your Sasha.
Can I have two apps open at once?
No. If an app is already open, Sasha shows "An app is already open. Close it before opening another." Close the first app with the X in the panel header.
Can an app read my sign-in or my other documents?
An app cannot read your sign-in or the Studio page, and cannot open your documents itself. It runs on a separate web address, in a sandbox with no network access, and the server checks your access on each operation. But an app that uses the chat can ask Sasha a question for you, and Sasha answers from the documents you can reach.
Who sees my time entries?
Only you. In Time Sheet Entry, each entry belongs to the person who made it. Projects are shared by everyone who can use the app.
What happens if two people change the same record?
The first save wins. The second save is refused because the record changed after it was loaded, and the app loads the current values again.
Does Claude change app records without asking me?
No. From Claude, Sasha asks you to accept each change first, and makes no change if Claude cannot show you the request. In a chat in the Sasha web interface, Sasha asks you one plain question in the chat, and makes the change only after you press the button that says yes.
The app will not load. Are my records lost?
No. Records are kept apart from the app's page. If the app page fails to start, a person with manage access sees the Raw data view, where they can view and edit the records. They can also open it from the ⋯ menu in the app panel header, with Edit raw data.
What are the roles with Set up next to them?
Digital team members, such as a Finance Agent or a Marketing Agent. Only an admin sees a role that is not added yet. Click it, then Set it up, and Sasha sets it up with you in chat. See the product guide page on team roles.
Can we remove a bundled app that we do not use?
Yes. Ask whoever runs your Sasha. They remove it and mark it so that updates of Sasha do not add it back.
Can I change an app or build a new one?
Admin and staff users with manage access can ask Sasha, in a chat, to change an existing app. They can also ask Claude to change it, when Claude is connected to Sasha. Changes go live as soon as the app passes its checks, with no draft and no undo. To add a new app, ask whoever runs your Sasha.
How much can I upload from an app?
Up to 10 files, 25 MiB (about 26 MB) in total, in one upload. The files go to the shared uploads folder, not to the project that is selected.
Why does an app say that it needs the Studio window?
The app was opened from another place, such as Claude. There, the app's own buttons cannot reach its records. Use the app in the Sasha web interface, or ask Claude to read or change the records directly.