Docs/Glossary
Glossary.
Every term you will see across the platform, defined. Sorted alphabetically. Bookmarked by every new hire on day one.
A to Z
- Account
- A CRM node representing a company or customer. Connected to Opportunities, Contacts, and Activities via graph edges.
- Action
- A single side effect the assistant performs (post a message, update a task, create a document). Every action is logged.
- Approval
- A workflow gate that requires named human sign-off before the workflow continues. Configured via the
[approvals]block in TOML. - Assistant
- A scoped program that reads from the work graph, calls a frontier model, and writes back. The runtime guarantees scope, audit, and replay.
- Audit log
- The append-only record of every action taken on the platform. Exportable to your own log store. Retention is configurable.
- Authentication
- Bearer tokens for API. SAML 2.0 or OIDC for users.
- Base URL
- The root of the wrxstack API at
https://api.wrxstack.com/v1. v1 is the only currently-shipped version. - BYO Model
- Bring-your-own-model. Run frontier models from your own provider (Azure OpenAI, Bedrock, Vertex, or self-hosted).
- Connected App
- In Salesforce, the OAuth registration that grants wrxstack permission to read and write. Created once per workspace.
- Contact
- A CRM node representing a person. Connected to an Account via an
aboutedge. - Contract
- A first-class node type for legal documents. Has versioning, redlining, and signature workflow.
- Cursor
- An opaque token returned by list endpoints. Pass it back as
cursor=to retrieve the next page. - Decision
- A graph node representing a captured choice. The audit log shows who decided and when.
- Deprecation
- Our policy: 12 months notice and a parallel-run window before any breaking change.
- DPA
- Data Processing Agreement. Available at /legal/dpa.html. Signed automatically as part of the standard MSA.
- Edge
- A typed relationship between two nodes in the work graph. Carries permission by default.
- Event
- A durable, ordered record of something that happened. Triggers fire on events. Webhooks deliver events.
- File
- A binary blob. Different from Document, which is structured prose.
- Graph
- See work graph.
- Group
- A set of users. Synced from your IdP or defined locally. Used in workflow scopes.
- Idempotency-Key
- An HTTP header on write requests. Two calls with the same key within 24 hours return the same response and produce only one side effect.
- Inbox
- The Inbox module. Triaged, drafted, and prioritized email under the same identity and audit as the rest of the platform.
- JIT provisioning
- Create a user on first SSO sign-in. Cheap to enable, slightly harder to clean up on departure.
- Module
- One of the twelve product surfaces (Tasks, Projects, Docs, CRM, Inbox, Meetings, Contracts, Forms, Documents, Search, Analytics, Assistant). All connected by the work graph.
- Node
- An addressable entity in the work graph. Every node has a stable id and a type.
- Opportunity
- A CRM node for a deal in progress. The most common subject of pipeline workflows.
- Permission
- A grant of read, write, or admin on a scope. Inherits along graph edges unless explicitly broken.
- Plan
- A workspace billing tier. Plans and their prices are set inside the product.
- Playbook
- A canonical document of your preferred contract or process positions. Referenced by the redline assistant.
- Policy
- A rule the assistant or the platform enforces. Examples: a variance threshold, an approval threshold, a retention floor.
- Project
- A grouping of tasks. The most common parent node for tasks; provides timelines and dependencies.
- Replay
- Re-execute a recorded assistant run against a sandbox. Used to diff workflow versions before promoting.
- Retention
- How long a class of data is kept. Configurable per workspace.
- Role
- A named bundle of permissions. Four built-ins: guest, member, lead, admin, plus custom roles on paid workspaces.
- Run
- A single execution of an assistant. Has an id, a status, steps, and an audit trail. Replayable.
- Scope
- The permission contract for a workflow or tool. Read scopes and write scopes are declared separately.
- Search
- The hybrid keyword + semantic query interface for the work graph. Permission-aware.
- Service account
- A machine identity. Created from Settings → API keys. Has its own audit lane.
- SSO
- Single sign-on. SAML 2.0 or OIDC. Required for production deployments at almost every customer we talk to.
- Step
- One row in a workflow definition. Calls an assistant or a tool, with optional
whenguard. - Tool
- A function the assistant can call. Has a name, a description, a schema, and a required scope.
- Trigger
- The event that starts a workflow. Either an event on the graph or a cron schedule.
- User
- A human identity. Authenticated via SSO. Provisioned via JIT.
- Webhook
- A signed HTTP POST delivered to your endpoint when an event happens. The push counterpart to polling.
- Workflow
- A TOML file under change control that ties trigger, scope, steps, and approvals together.
- Workspace
- The top-level isolation boundary. Two workspaces share no data, no graph, no audit.
- Work graph
- The unified data model behind wrxstack. Every artifact is a node; every relationship is an edge.