How to Manage Security Models and Branch Types

Create or edit a policy template (Security Model) that a sub-organization inherits when created under one of its Branch Types. See Security Models and Branch Types first if these terms are new.

Before you start

The Configure System right.

Steps

1. Go to Settings → My Account → {Branch} Types.
2. Click Add Model, or click an existing model to edit it. A model has four tabs:
   • Model Config — name (required), description, Branch Type chips (each with its own enable/disable dot), whether owners can view other organizations, and whether sub-child organizations are allowed under this one.
   • Censorship — allowed member/team-member age ranges, and per-topic (alcohol/tobacco/firearms) policy: member-select, not allowed, or always allowed.
   • Allowed Apps — per app, one of Optional (default on), Optional (default off), Not Available, or Force-Enabled — plus which commerce types (Retail, Mortgage, Rental, etc.) are allowed for apps that support markets.
   • Default Security Roles — pre-set rights (Force-Granted / Granted / Not Specified / Force-Nuke / Nuke) per role type for organizations created under this model.
3. Save is blocked until the app catalog has finished loading — this is deliberate, since saving early would otherwise wipe app grants you hadn't touched yet.

To remove a Branch Type

Deleting a chip checks first whether any organization is currently using it. If so, deletion is blocked — disable it instead (click its status dot), which hides it from the org-creation flow without breaking existing organizations already using it.

To delete a whole model

Click Delete, confirm: "Are you sure you want to delete the security model '{name}'? This cannot be undone." There's no in-use check before deleting an entire model, unlike deleting a single Branch Type — double-check nothing depends on it first.

The Master Model

Click Edit Master Model to configure the top-level organization's own capabilities, using the same tabs minus Branch Types.