Skip to main content

Organization administration

An organization is the top-level administration, security, environment, operations, analytics, and billing boundary. Its secondary navigation exposes Members, Teams, Solutions, Roles, Policies, Environments, Execution History, Integration Activity, Retention Policies, Statistics, and Settings.

Members and invitations​

To invite a member:

  1. Open Organization → Members.
  2. Enter the member's email.
  3. Select an organization role.
  4. Optionally select a solution and solution role.
  5. Optionally add one or more teams.
  6. Send the invitation.

Example author invitation:

Email: author@example.com
Organization role: Member
Solution: Lending
Solution role: Editor
Teams: Lending Authors

Pending invitations can be reviewed or cancelled. Access becomes active only after acceptance. Removing a member affects organization access but should be coordinated with ownership of API keys, connectors, deployments, tests, and pending work.

If SSO is required, invite a corporate-domain address. DecisionHub uses the identity provider for authentication while the invitation, roles, and policies still control authorization.

Teams​

Teams group users who need the same access. Create a team with name, color, description, and members. Use names such as Lending Authors, Release Approvers, or Production Support.

Team membership itself is not a complete permission definition; policies assign roles to the team. A member can also have direct policies, so removing them from one team may not remove all access.

Roles​

Roles group permissions. System roles cover common responsibilities; custom roles let administrators select a tailored permission tree. Describe the business responsibility and avoid broad “all access” roles when a narrower one is practical.

Before editing a role, identify every member/team policy that uses it. A change can affect many users and solutions immediately.

Policies​

Policies connect a role to a member or team and optionally a solution. Example:

Subject: Release Approvers team
Role: Deployment Approver
Scope: Organization
Subject: Lending Authors team
Role: Decision Author
Scope: Lending solution

Effective access is additive across applicable policies. Use the Access control guide to troubleshoot missing or unexpected actions.

Solutions​

Solutions separate business workspaces and access. Organization administrators can create/manage them, while solution roles determine who can work in each Hub. Review inactive or unused solutions before deleting them because they can own deployed assets and credentials.

Environments and deployments​

Environments define the release sequence. Deployment Requests provide selection, dependency preview, approval, execution, and audit. Organization permissions can separate request creation, approval, and deployment execution.

Execution History​

Filter by:

  • correlation ID;
  • HubItem type;
  • executing user/service where available;
  • start and end date.

Open a record to inspect request, response, timing, and permitted debug information. Example support flow:

Customer reports APP-1042
  → find correlation/business ID
  → filter Execution History
  → inspect deployed Workflow and node trace
  → follow connector activity if external action failed

Manual deletion requires permission. Prefer Retention Policies for consistent lifecycle management.

Integration Activity​

Filter by trigger/publisher adapter, pending/processing/succeeded/dead-letter status, provider, and endpoint. Open an activity record to inspect transport details and follow its linked execution. Sensitive payload visibility remains permission-controlled.

Retention Policies​

Create a policy with:

  • organization-wide or specific-HubItem scope;
  • retention period;
  • whether debug data is also removed;
  • enabled state.

Example:

Scope: Personal Loan Decision Workflow
Retention: 3 months
Delete debug data: Yes
Enabled: Yes

Scope cannot be changed after creation. Edit the period/options, enable or disable, delete, or Apply now with permission. Apply now permanently removes records older than active limits; confirm scope and legal retention requirements first.

Statistics​

Statistics summarizes API calls and supports solution search. Use it to identify unusual volume or trends, then inspect the relevant solution API-key activity and Execution History.

Settings and SSO​

Settings include organization options, analytics availability, and SAML SSO when supported by the plan. Organization analytics must be enabled before supported HubItems can persist analytics records. SSO configuration remains invitation-based and should be tested before enforcement.

Administrator checklist​

  • Review active members, pending invitations, teams, and policies regularly.
  • Keep solution ownership current.
  • Separate production debug and deployment permissions.
  • Review environments, active API keys, connectors, and event health.
  • Define retention before enabling broad analytics.
  • Rotate external and platform credentials.
  • Preserve audit records for role and deployment changes.