Glossary
Organization
Your space in RuleForge. Each company usually has one organization, which holds members, projects, integrations, and billing.
Project
Where work happens. Each project groups your rules, decoders, test cases, reviews, and versions.
Workspace
A personal draft. It preserves your editor's current state so you can come back later, without creating a formal version yet.
Test case
A repeatable test. A sample event (log) with the result you expect — useful to make sure a rule keeps working the way it should.
Regression
Running all your test cases at once, typically before publishing. If something broke, regression warns you before content reaches production.
Review
The moment to request approval before publishing. Equivalent to a pull request inside RuleForge.
Version
An official snapshot of the project, ready to publish. Versions have history and can be compared.
Quality criteria (quality gate)
The list of checks that need to pass for a version to be publishable. For example: zero errors, all cases passing, approved review.
Integration
Connecting RuleForge to your environment's tools: Git, CI pipelines, Slack/Teams, ticket systems, etc.
Git connection
The credential that connects your organization to GitHub, GitLab, or Gitea. Lives at the organization level and is reused by projects.
Git link (per project)
The configuration that says which repository and branch a RuleForge project mirrors.
Pull request / Merge request
The merge request on your Git provider. RuleForge can open one automatically at publish time if that's your strategy.
Webhook
An automatic notification. When something happens (a published version, a failing regression), RuleForge notifies an external system via URL.
SSO (OIDC)
Signing in to RuleForge with your company's existing login (Google, Okta, Entra ID, etc.). Avoids another password.
SCIM
Automatic account provisioning. When someone joins or leaves the company, the RuleForge account follows.
API key
A credential that lets an external tool use RuleForge on your behalf — for example, an internal script or automation.
Audit
The organization's action history: who did what, when.
Role
A person's access level — administrator, content lead, reviewer, engineer, read only.