Administration

Organization management is in Settings → Organization. Administrators manage the organization. Members can read its profile, external-provider permissions and experiments; member management, groups and usage require an administrator.

Organization pages

• General — organization name and report privacy, with summary links to members, groups, usage, providers and experiments for administrators. Detailed source context in reports controls whether report generation receives source headlines, links and event details. When off, reports use topic summaries and counts.
• Members — search members, invite users, manage pending invitations, change roles and open per-user usage details.
• Groups & permissions — search groups, manage members and assign access to Repository files.
• Usage & plan — current plan and billing cycle, storage and AI token totals, accessible files, member count and resource allowances. The member breakdown opens automatically, with names, token shares and totals by activity. Background usage appears separately. Hide breakdown collapses it.
• External providers — providers that receive organization data, the processing purpose, data shared, dependent functions and the consequence of disabling each permission.
• Experimental features — separate opt-in controls for optional Advisor and global-search assessments and generated alert banners. Each experiment also requires its provider permission and service availability.

Administrative visibility does not replace organization feature access or record-level permissions. The accessible-file count follows the current administrator's file access. Unlimited allowances are shown as unlimited; missing usage data shows a retry state.

Roles

• Admin — manages the organization and its settings.
• Member — uses the enabled features and resources shared with the member.

Changing a role takes effect through authenticated workspace permissions. Refresh or sign in again if a surface still shows the old role.

Provider permissions and consequences

Permissions apply to the processing purpose shown in each row. Multiple rows can name the same provider because different functions have independent controls.

Services in use lists purposes available to the organization's enabled features. Automatic fallbacks lists services that can receive data when the primary path is unavailable. Inactive services and permissions is collapsed initially; expand it to review or withdraw stored permissions. Allowing a provider does not by itself activate an experiment or an unused service. Availability unverified appears when service availability cannot be confirmed.

Disabling external alert judging stops new AI alert matching and delivery. AI judging in smart folders also stops, while structural filters and manually selected content may remain available. Disabling the Advisor provider prevents new Advisor work. Disabling report generation prevents new reports. Existing conversations, reports and stored content are retained.

External document analysis controls the external processing described in its permission row. When disabled, supported file processing remains available, but uploads or analysis that require that provider can fail. Check the listed consequences before changing the permission.

Disabling cloud image assessment stops licensed-image selection. Generated banners have a separate provider permission and experiment. Other permissions describe their own fallback or unavailable function in the table; disabling one purpose does not disable every external service.

Changes apply within 60 seconds. New Advisor and optional assessment requests check the latest permission. Requests already processing may finish.

Saving and loading errors

Organization changes require Save changes. Disabling a provider or allowing detailed report context opens a confirmation explaining its effect. Unsaved changes remain visible if a save fails. If another administrator changed the same setting, reload the latest values before retrying.

If a workspace allowance is exhausted, eligible AI background work can be skipped and interactive AI actions can be rejected until the allowance resets or the plan changes. Existing content remains available according to its access rules. Usage is an operational summary, not an invoice.

Pages in this section

• Users and groups — invitations, roles, membership and file access.