One workspace, one connected record.
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.
What a meeting turns into
Notes are a record; work moves. Scripta keeps them as separate objects because they behave differently.
Meetings
The transcript you bring in, record from your own browser (every plan, behind a consent step), or type as notes, plus the summary generated from it. Each keeps its source, date and state.
Decisions
What was agreed, the reasoning, and the excerpt it came from, tracked to an outcome: delivered, moving, drifting or stale.
Action items
Work with an owner, a due date and a status. The assignee can be someone without an account, recorded by email.
Documents and comments
Attachments and threaded discussion on the meeting that produced them. PDF, Word, PowerPoint and text uploads are read on arrival, so search finds a document by what it says.
Projects
Where decisions and their work are filed across the meetings that touched them. Health is worked out from its own rows. No status dropdown, no progress bar.
People and companies
Your team, plus everyone who was in a meeting. Companies are derived from those addresses’ domains. Nothing is entered by hand.
The Inbox
What needs a person: decisions drifting or stale, recordings that failed, projects at risk, and proposals from extraction or the Scripta AI Agent waiting to be accepted or dismissed. Every item is worked out fresh from the record on each load, so it leaves on its own once the thing is fixed.
Bring it in however it was captured.
- Record in your browser: microphone, or a tab plus your mic, behind a consent step. Scripta doesn’t join your calls.
- Paste or upload: copy a transcript out of whatever captured it, or upload the audio or a PDF, Word or text file.
- Import a calendar file: the .ics your calendar exports for an event fills the meeting form. It reads the file; no calendar account is connected.
None of these is a connected integration. There is no account to link and nothing is fetched on your behalf. Pushing action items back out to Slack, Notion, Linear or Jira isn’t built either; when either one 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.
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.
Enforced at the database level
The check lives on the data.
Hiding a button is never the only thing standing between a request and somebody’s meeting.
Guests are scoped per workspace.
External guests get the same four roles. A client sees their workspace and nothing else.
One write-up, to anyone.
An unlisted link rather than a public page, protected by a passcode, revocable whenever you like, and kept out of search engines.
See it on a real meeting.
Paste a transcript you already have and look at what comes back.
No credit card required.