Meetings
The transcript or notes you bring in, plus the summary generated from them. Each one keeps its source, date and processing state.
Scripta takes what a meeting produced and files it as things that behave correctly — a record that stays findable, and work that has an owner. Here is what the product actually consists of.
Notes are a record; work moves. Scripta keeps them as separate objects because they behave differently.
The transcript or notes you bring in, plus the summary generated from them. Each one keeps its source, date and processing state.
What was agreed, the reasoning behind it, the date, and the excerpt it came from — filed under the topic so it's findable without remembering which meeting produced it.
Work with an owner, a due date and a status. The assignee can be someone without an account, recorded by email.
Attachments and threaded discussion attached to the meeting that produced them, so a follow-up question keeps its context.
Scripta doesn’t join your calls. Bring the transcript from whatever captured it, or paste your own notes.
Pushing action items out to Slack, Notion, Linear or Jira isn’t built yet — when it is, it will be listed here rather than promised.
Permissions aren’t a UI convention. A request for a workspace you aren’t a member of returns nothing, rather than returning data the interface then hides.
| Role | Can do |
|---|---|
| Viewer | Reads everything in the workspace. |
| Commenter | Reads, and can post comments — but can't change the record. |
| Editor | Creates and edits meetings, decisions, action items and files. |
| Admin | Everything an editor can do, plus managing who's in the workspace. |
External guests get the same four roles, scoped per workspace — a client sees their workspace and nothing else. There are no public share links; access is always attributable and revocable.
Paste a transcript you already have and look at what comes back.