3. Workshop: folders
Workshop works like a file explorer. On the left: My Workshop (yours alone), then Shared folders, Schedules, Recently deleted, New shared folder. One click opens an item. ⋯, a right click or a long press (phone) opens its menu. Select acts on several items; on a computer, drag and drop moves them.
3.1 Kinds of folders
| Kind | Who | Data |
|---|---|---|
| My Workshop | you | your personal data |
| Shared folder | its members (and its owner) | data shared by the members |
| Sub-folder | same people as the folder it's in | same data: it only tidies |
| Folder with separate data (lock icon) | only the people you choose | its own data, kept apart |
Where a tool lives. Every tool lives in one folder, its home: My Workshop, or a shared folder. There it shows as a tool; anywhere else it is a shortcut (small arrow, "lives in …"). Opened without choosing a folder (from its page, from My tools), a tool opens at home, with its home's data. My Workshop only shows the tools that live there: tick Also in shared folders to see all the tools you make. To change a tool's home: ⋯ → Make it live in… (makers).
A tool finds its tables by name, in the folder it is opened from. So the same tool can serve two folders, each with its own data, as long as each has the tables. When a tool with tables arrives in a folder that lacks them (Create shortcut in…, Make it live in…), Blackslate offers: Create the same tables here, empty, Copy the tables here (today's data, then each folder lives its own life), or Nothing for now. Opened in a folder that lacks them, the tool shows "This tool needs tables that … doesn't have", with Create them here (missing tables are created empty, missing columns added empty; existing data is never changed) and Open it in … (its home).
A tool's tables are listed under it. In the folder where a tool lives, its tables (those of its table plan) are tucked under it: 8 tables ▸ unfolds them, a second tap folds them. A table used by two tools shows under each ("also used by …"). Tables no tool uses are grouped under Other tables. This only tidies the list: the tables stay in the folder, with their usual ⋯ menu; Select unfolds everything.
Public link… (⋯ on a tool, for people who can edit the folder; shown for a tool that uses an inbox, a showcase or calendars): links that open the tool for anyone, without an account, to send orders, bookings or sign-ups to its inbox. Each link can be copied, printed as a QR code, turned off, replaced by a new one (the old one stops working), or given a daily limit. What visitors send arrives in this folder; they can't read anything.
Publish with a tool… (⋯ on a table, for the folder's owner or admins): the table becomes reference data for one of the tools you make. Everyone who uses that tool reads it, read only, in its current version, wherever the tool is used (and its copies, if you allow it). It is said before publishing: everyone reads every row, so never personal data, and never a protected table. The tool's Makers and publishing (on its Edit tool page) lists its published tables, with Unpublish. Tables published from Blackslate's storage are limited to 10 MB in all; beyond, publish from your own storage (chapter 6).
Web services (⋯ on a folder, for its owner or admins): the addresses the folder's tools may call (window.leavenit.web, chapter 5) and its flows may send rows to (Send to a web service, 4.12), through the folder's Runner, with or without a key. A key is kept in Blackslate's vault, bound to its address; the Runner adds it, tools never see it. The list shows each service's calls of the day (from tools, from flows) and the flows that send to it; Remove stops it at once.
Data warehouses (⋯ on a folder, for its owner): the databases, cloud warehouses and data lakes the folder's blocks may read (PostgreSQL, Redshift, Snowflake, BigQuery, S3…), through the folder's Runner, with Browse to see their tables (chapter 4.7). Members who can edit see them by name. With Writing on, in one schema the owner chooses, blocks can also send their tables back (chapter 4.8). Live queries lists the queries the folder's tools may call live (chapter 4.9).
Moving an item never moves its data. Move to… tidies an item inside the same folder; to put a tool in another folder, use Make it live in… or Create shortcut in…. A table or a flow can't leave its data area: "Its data belongs to another folder: it can't move there."
3.2 Shared folders
- New shared folder (left column) → a name → Create.
- Its ⋯ (next to its name): Members and invite link, Storage, Runners, Data and activity, Rename, Leave, Delete.
- Members and invite link: Copy link (anyone with the link can join), New link (the old one stops working), Turn off / Turn on invitations, Remove a member.
- Joining: open the invite link → Join group.
- Dev · Test · Prod (next to its name, for admins and members who can edit): the three versions of the folder, each with its own tables, flows, warehouses and version of the folder's tools; Prod is the one everyone uses. Promote to Test…, Promote to Prod… carry tool versions, flows and the columns of tables from one to the next (chapter 4.11).
3.3 Folders with separate data
Only the owner of the shared folder creates them: New folder → Keep this folder's data separate. Then its ⋯ → Manage access: Everyone in
3.4 Adding things
Add (top right of a folder): New tool (My Workshop, or an organisation for its creators) or Shortcut to one of my tools… (shared folders), Import a file (table) (a CSV becomes a table), Import a tool (.zip) (a tool exported from Blackslate, chapter 3.7), Import a flow… (a flow your AI wrote, chapter 4.6), New flow, New note (a text in Markdown, 3.10). New folder creates a sub-folder.
3.5 Recently deleted
Deleting a folder sends it to Recently deleted for 30 days, with everything inside. Restore puts it back. After 30 days: shortcuts leave the shared folder (the tools themselves are never deleted), tables and flows inside are deleted. Deleting a folder that contains tables or flows needs the right to manage its data.
3.6 Data and activity
⋯ → Data and activity: the data saved by tools in this data area (filter by key, Export JSON, Export CSV) and the activity log.
3.7 Exporting and importing a tool
⋯ on a tool → Export, for everyone who has the tool: one .zip with the tool and its data where it is opened, in an open format that doesn't need Blackslate.
| In the .zip | What it is |
|---|---|
leavenit.json |
name, description, category, its tables and what the .zip holds |
FORMAT.md |
the format explained, for a person, an AI or another service |
index.html (or pages/…, shared/… for an app), icon.png |
the tool and its icon |
tables/<name>.csv |
each of its tables, as it is in this folder |
data/me.json |
what the tool saved for you (its localStorage included, keys ls:…) |
data/shared.json, data/private.json |
in a shared folder: the folder's shared data, and the private answers you can read (a manager reads everyone's) |
files/… |
the photos and files the tool kept, as they were sent |
notes/<name>.md |
the folder's notes about the tool (3.10); they come back with it on import |
Add → Import a tool (.zip): Blackslate reads the .zip and says what it holds, then makes the tool again, private, in the open folder: its tables (created, then filled), what it saved, its files (with new ids, written back into its data and tables). Nothing that already exists in the folder is ever replaced: a table or a shared value already there is kept as it is, and the message says so. Not imported: the rows of a protected table (they belong to each member) and other members' private answers and files. Shared data only goes back into a shared folder.
3.8 Organisations (companies, associations)
An organisation is a shared folder for a company or an association: it has admins, it invites people by e-mail, and the accounts it invites are work accounts, tied to it.
- Create one: Workshop → New organisation → a name → Create the organisation. You are its first admin (your own account stays personal). Everyone in an organisation Can view by default; creators and admins get more.
- People (⋯ next to the organisation's name, or the round button's menu): Invite people (e-mail addresses, one per line, as User or Creator) → Send the invitation. Each person gets an e-mail with a link (or Copy link to send it yourself); an invitation lasts 14 days, Resend makes a new link, Cancel stops it. Members: change someone's profile (User / Creator) in one tap; ⋯ → Make admin or Remove admin, Remove from ….
- Joining: the link opens Join …, with the invited address filled in. The person chooses a password and gives their name (shown to colleagues and to tools) → Create my work account, confirms their e-mail, and lands on the organisation's tools. An address that already has a Blackslate account can't become a work account: invite another address (usually the work one).
- User: sees only the organisation's tools they can open, in My tools (nothing to pin); no Showcase, no Workshop, no Add a tool. Creator: the Workshop of the organisation (no personal My Workshop), Add → New tool; their tools live in the organisation. An organisation's tools never go on the Showcase (By link is possible).
- My tools of a work account: first the organisation's pages, the same for everyone and locked (🔒 Arranged by the admins): its tools (each person sees only those they can open), websites, apps, folders and groups. Then their own pages (My shortcuts at first): with (+) they add websites, apps, folders, groups and pages, but no tools (their tools are on the organisation's pages). A tool newly given to someone arrives at the end of the organisation's first page until the admins place it.
- Arranging the organisation's pages (admins): People → Home (+ Add, Arrange), or directly in My tools for an admin with a work account (you arrange it for everyone): add websites, apps, folders, groups and pages, and drag the tiles as in chapter 2.7. The organisation's tools are all there already: they are moved, never removed. Another admin changing the pages at the same moment: the second is told and sees them again.
- Who opens what: put tools in folders with separate data and use Manage access (chapter 3.3). The strongest right always wins, so a person can only be given more than Everyone: to give someone less, lower Everyone first.
- Removing someone cuts all their access at once. A work account is closed (it can't sign in any more); what they wrote stays with the organisation, and the admin who removed them becomes a maker of their tools. Closing someone's e-mail address isn't enough: remove them on the day they leave.
- Several accounts on one device: the round button's menu lists the accounts opened on the device; Switch changes account in a second, Add an account signs in to another one, Sign out of this account ends only the one in use. A personal account's round button is light when the device also has a work account.
3.9 Directory and who sees which rows (organisations)
In an organisation, an employee doesn't always have the right to see every row of a table: a sales rep sees the clients of their region, the sales director sees them all. Blackslate does it without anyone keeping rights up to date by hand: a directory says who has which values, and each table has a rule, written once.
- The directory (organisation's People → Directory, for admins): one row per person, found by their work e-mail, with the columns of its source (region, agency, department, manager…: the source decides). Choose a source:
- A table in a folder: kept by HR in Blackslate, or, better, made by a flow whose SQL blocks turn the raw HR export into a clean table. The directory follows the table each time it is written (by the device that wrote it: a scheduled flow runs on a device that is on, or on your Runner). Update now reads it again. Put this table in a folder with separate data that only admins and HR can change: whoever changes it changes who sees what.
- A link, read every night: an export your HR software puts online (CSV over https), or a Google Sheets sheet published as CSV. Blackslate reads it itself at 2:00 (Paris time), no device needed; Update now reads it at once. If it can't be read (wrong address, no e-mail column), the directory doesn't change and the reason is shown.
- A file, now and then: a CSV with a header row; Upload the new file each time.
- People who leave lose their rows at once. Close the work account of people who leave the directory (ticked by default) also closes their work account, like Remove in People (never an admin's). An update that would make many people leave at once (more than 3 and more than a fifth) is put on hold, not applied: a broken export can't empty the organisation. An admin sees it in Directory and chooses Apply it or Leave it.
- Each update says what changed: arrivals, changes (Marie: region West → South), departures. Rows without a valid e-mail, and e-mails found twice, are set aside and shown, never guessed: those people see no rows until there is one row each. Several values in one cell are separated by commas (South, West). A directory holds up to 20,000 people.
- The rule of a table (⋯ on a table → Who sees which rows…, for admins of the organisation or of the folder). Rows by person: a row is seen when one of the conditions gives it to the person (up to 4):
- By directory column: the row's column is one of their directory column values (their region, their agency…). A row with no value: only admins see it.
- By person: the row's column is them, compared with one of their directory columns, best their e-mail (two people can have the same name; capitals and spaces around are ignored).
- By team: someone in their team sees it. The team comes from a directory column holding each person's manager's e-mail, at all levels: a manager sees what the people under them see.
- See every row: people whose directory column is one of the values given (for example Service = Direction commerciale) see every row, without being admins.
- Tables of reference and chains: Follows another table — a row is seen with its row of table, linked by column. Like a table of reference in a Power BI model: write the rule once on regions, and ventes (by region_id), then lignes_vente (by vente_id) follow, down a chain of up to 4 tables. The dialog guesses the link (a column client_id next to a table clients, a column region next to regions) and, on a table with a rule, lists the tables that could follow it: Follow in one tap. Rows of linked tables move with their main row.
- Changing a rule on a table that already has rows is possible: every row is put in its place again (on the admin's device), with the tables that follow it. Everyone who can open the folder sees every row removes the rule: the rows go back into the table first.
- Admins always see every row (admins of the organisation, and Can manage of the folder). Someone who isn't in the directory, or whose values match no row, sees none (refused by default: a mistake in the directory hides rows rather than showing them to the wrong person).
- Rows already in the table are put in their place right after Save.
- See as… (People → Directory, for admins): choose a person and see what they receive from each table with a rule (3 of 1,532 rows, and by which condition: their region, as responsible, their team), before counting on it. To look at lists what needs a look: rows nobody in the directory can see (an empty or unknown value), accounts that aren't in the directory (they see no rows), people no rule gives a row, people of the directory without an account yet.
- What changes for people: nothing to learn. A tool shows them only their rows; the others never reach their device. Writing a row of a value they don't have is refused (not_your_rows): a rep of the South can't put a client in the West; an admin, or someone who covers both, moves it.
- When the directory changes, nothing in the data moves: the next time someone opens a tool, they get the rows of their new values.
- Comparing with the whole organisation (my region against France): an admin makes a summary table, totals only, readable by everyone, rebuilt every night by a flow (chapter 9.12). A block or a flow reads a table with a rule whole only when an admin runs it; for anyone else it is refused, and a block can't write into a table with a rule. A protected table (rows kept per author) can't have a rule or follow a table.
3.10 Notes
A note is a text in Markdown kept in a folder, like a table or a flow: how a tool is used, the rules of a team, a to-do list, a page to read first. Everyone who can see the folder reads it; those who can change the folder write it.
- New note: Add → New note (free in the folder), or ⋯ on a tool, a table or a flow → New note about this tool (… table, … flow). A note about a tool is shown under it, with its tables (the button 4 items ▸ unfolds them); a note about a table or a flow says note · about …. ⋯ → Notes (2) opens them.
- Reading and writing: a note opens read (titles, lists, bold, links, tables, boxes to tick). Edit shows the text, with buttons that write the Markdown for you (B, I, Title, List, To do, Link) and Preview; Save (or Ctrl+S / ⌘S). Ticking a box while reading saves it at once.
- History: each save is a version (who, when); the last 20 are kept. Open one to read it, Restore this version puts its text back as a new version.
- Two people at once: there is no writing together live. If someone saved while you were writing, Blackslate says so and keeps your text: Save mine anyway (theirs stays in History), or Save mine as a copy (a new note).
- ⋯ on a note: Rename, Attach to… (a tool, a table or a flow of the folder, or nothing), Copy the text, Download .md, Delete (to Recently deleted, 30 days). Move to… in the folder's ⋯, like any item; a note stays in its data area (it can't move into a folder with separate data).
- For your AI: the notes about a flow are added to its Copy for my AI text (4.6), and the notes about a tool to the change prompt of its Edit page (a tool in one file). Rules written once serve every change.
- Export of a tool (3.7): its notes in the folder go with it (
notes/<name>.md) and come back, about the new tool, when it is imported. The descriptions of its tables (4.13) go with them too. - A note belongs to its folder: a shortcut to the tool in another folder doesn't show it. Text only (200,000 characters): no images yet, a link to a file is fine. HTML written in a note is shown as text, and links open only
https://andmailto:addresses.
3.11 Usage of my tools
The makers of a tool (its author and the makers they added) see how many people use it, never who. In the workshop: Usage of my tools (left column) lists every tool you make, by the number of people over 30 days, with the trend, who comes back and the errors; on a tool you make, the line under its name says 312 people this week once others use it, and ⋯ → Usage opens its page (also in the tool's ⋯ menu).
- The four figures: Opened (each opening, online), People (with an account, each person once; without one, once a day, hence the ≈), Coming back (among people with an account: used it on 2 days or more), Kept something in it (people who saved data, a row, a file or a form). Over 7 days, 30 days or 12 months, compared with the period before.
- Every day: the openings (bars) and the people (line), with a mark where a new version was saved.
- Where they come from: its page in the gallery, a shared link, installed as an app, a team's folder, a workshop, a public link. On what: phone, tablet, computer.
- From its page to its use (a public tool, or one shared by link or sold): people who saw its page, opened it, added it to their workshop, bought it.
- What people do in it: the actions the tool counts itself with
window.leavenit.track('name')(5.2). Ask my AI to count actions opens its Edit page with that request already written. - What breaks: the errors the tool didn't catch, by their first line (e-mail addresses and long numbers removed), how many times, how many people, which version, on what. Fix with my AI opens its Edit page with the errors and the request to fix them, ready to copy for your AI.
- An app (several pages) also shows how many people opened each page.
- What isn't counted: your own uses and the other makers', a tool opened offline, Try it before saving. A team's tool is counted like the others: exact numbers, never a name.
- Privacy: counts only. No IP address is kept, no cookie is set. A person with an account is counted from a code made for that tool; without an account, from a code of the day (from their connection and browser, and a key deleted the next day), so the same person on two days counts twice. Kept 13 months. People who use a tool read in its ⋯ menu: Its maker sees how many people use it, never who.
3.12 Health
Health (left column of the Workshop, with the number of things to look at; nothing when all is fine) gathers on one page what asks for an action, for what you make and the shared folders you manage (their admins see all their flows and Runners; everyone sees the flows they made and the tools they make). A filter by folder, and the last 7 or 30 days.
- To look at, the most serious first, each with the button that deals with it: a flow whose last run failed (how many times in a row, the block, the error; Copy for my AI, Open the flow), a Runner offline or that missed schedules (and which flows), a paused schedule (Review), rows a web service refused (4.12), a flow that took 3 times its usual time or more (a sign before it fails), a tool's errors (as Usage counts them, 3.11: Usage, Fix with my AI), new feedback.
- Flows: each scheduled flow (and a flow run by hand whose last run failed): its runs of the period (green done, red failed, yellow missed), its success rate, its last run, its usual time (the median of its 10 runs before, from 5 runs), its next run.
- Tools: the tools you make: their errors and the people who hit them, the most frequent one, and their open feedback by kind.
- Feedback (also ⋯ on a tool you make → Feedback): every feedback on your tools, open or done: its kind, its text, the version, when, and who (only when the person allowed an answer; otherwise Anonymous). Its state: New, Seen, Planned, Done. Answer (when allowed) sends a notification to the person. Fix with my AI (a bug) opens the tool's Edit page with the feedback, ready for your AI.
Feedback from the people who use a tool
In a tool's ⋯ menu, for the people who use it (with an account; not its makers): Send feedback. What it is about (something's wrong, an idea, a question, I like it) and a text (2,000 characters). It is anonymous unless The makers may answer me is ticked: its makers then see the name and can answer (a notification; the answer is under Send feedback, with the person's earlier feedback). Sent with it: the tool's version, nothing else. 10 a day per person and per tool. Its makers get a notification for each one (in Blackslate, no e-mail).
3.13 AI agents (MCP)
An AI agent (Claude, or another AI app that speaks MCP, the Model Context Protocol) can work in Blackslate for you: read your folders, find what fails, document tables, prepare changes. It works with your rights, only in the folders you choose, and it changes only their Dev version: Test and Prod wait for you.
- Connect (Profile → AI agents): Blackslate's MCP address is
https://leavenit.com/mcp.- Claude (web, desktop, phone): Settings → Connectors → Add custom connector, paste the address. Claude opens Blackslate: tick the folders it may work in (none at first), then Allow. It says which address it goes back to (claude.ai); an app that goes back to localhost runs on a computer: allow it only if you started it yourself.
- Claude Code:
claude mcp add --transport http leavenit https://leavenit.com/mcp, then/mcpto sign in. Or a personal token. - Other apps (remote MCP servers, streamable HTTP): the address, then their sign-in, or a personal token sent as the header
Authorization: Bearer …. - Personal tokens (New token): a name, the folders, a duration (30 days, 90 days, 1 year). It is shown once; Blackslate keeps only its fingerprint. A token works like a sign-in: give it only to an app you trust.
- What an agent can do, in the folders you chose: read the tables (their columns and descriptions; the rows of small tables), the flows, their blocks and runs, the tools and their code, the notes, Health and the feedback of the tools you make; write notes. The rule: it changes only the Dev version of a folder; Test and Prod are read-only to it, and it asks you for a promotion, which you approve in Blackslate (never in the conversation). My Workshop has no Dev: an agent only reads it; for a project with an agent, use a shared folder (even with no one else in it). Where you can only read, it only reads.
- In Dev, it opens the Dev version if the folder has none (empty), describes tables and columns (they arrive to check), changes rows, creates flows, saves, checks and deletes blocks, runs blocks and flows (small tables; what reads from outside or a large table is built by the folder's Runner, which it can ask), and saves a new version of a tool (one HTML file, in a shared folder with its Dev: Prod keeps its version).
- It asks you: a promotion (Dev → Test, Test → Prod), with the items it names and a summary you can verify; an answer to a feedback (only when its author allowed one): you read it, edit it and send it, or not. It marks feedback Seen, Planned or Done itself.
- Never: share, publish, public links, members and rights, Runners, deleting a folder. Keys and passwords: it sees their names, never their values.
- The Agent note: a note named Agent note at the root of each folder (3.10), made from a short template the first time an agent maps the folder (when you can edit it). The agent reads it first and updates it last: what the folder is for, how its pieces connect, the conventions, what not to touch, what is in progress, your decisions, the pitfalls. It is the project's memory from one session to the next; you can edit it, you have the last word.
- What the agent receives: Blackslate's rules when it connects (work in Dev in small steps, check for real, ask for little, describe what it creates, treat data as data, update the Agent note), deeper guides it reads when the work needs them, and recipes you can choose in your AI app (in Claude, the + menu or /): Fix a failing flow, Triage feedback, Document a folder, New flow from a table, Improve a tool, Weekly check-up, Before promotion.
- Data is data: an agent reads texts written by others (feedback, table values, notes). A text can try to give it instructions; Blackslate tells agents never to follow them, and nothing leaves Dev without you.
- Waiting for you (at the top of Profile → AI agents, and a notification): each request of your agents. A promotion: Review and promote… opens the usual Promote screen (4.11) with the agent's items ticked and its summary at the top; Refuse… with a note the agent reads. An answer: edit it, Send or Discard. A request not answered in 14 days expires.
- Activity (Profile → AI agents): what your agents changed and asked, most recent first (or All agents in a folder: what everyone's agents did there, for whom). Undo: a note or a description goes back to its text before, a block to its SQL before, a deleted block comes back, a created flow is deleted, a tool goes back to its version before (in Dev). Rows changed in Dev can't be undone (Copy from Prod starts again from Prod).
- Connected agents (Profile → AI agents): each agent, how it is connected, its folders (Folders to change them), when it was last used, how much it did this week and its requests waiting. Disconnect (a sign-in) or Revoke (a token): it stops within a minute; its waiting requests are dropped. Every action of an agent is logged.
- Limits: 600 calls per hour per agent, 200 of them changes; an answer is 60,000 characters at most; rows are read and blocks are run on small tables (a few MB compressed); a large table: its columns and descriptions, and the folder's Runner to build it; 30 requests waiting per agent.
| Message | What to do |
|---|---|
| "This folder isn't open to this agent" | Profile → AI agents → Folders, tick it |
| "An agent changes only the Dev version of a folder" | the agent works in Dev, then asks for a promotion |
| "This sign-in belongs to an AI agent: it works only through Blackslate's MCP server" | an agent's sign-in can't be used elsewhere: connect the app by MCP |
| "This agent isn't connected to Blackslate (or no longer is)" | connect it again (the token expired, or it was disconnected) |