Account settings

Account settings establish an organization’s identity, security baselines, and workspace defaults. Configured at the enterprise level, these settings shape every user’s workspace experience, ensuring brand consistency and enforcing administrative policy without requiring individual setup.

Organization profile and branding

The organization profile defines your enterprise’s visual and corporate identity across the Rival platform:

• Organization name — the primary legal or business entity name displayed across system portals, communications, and administrative reports.
• Logo and visual identity — the custom branding assets rendered across workspace navigation headers, agent interfaces, and generated export documents.
• Branded environment — establishing these profile details early ensures that new team members experience a fully branded, recognizable environment from day one.

Workspace defaults and governance baselines

Workspace defaults define the baseline environment for every newly onboarded user and newly created automation project:

• Default user roles — establishes the starting permission level for newly invited team members, such as assigning the standard Enterprise Team Member role upon invitation.
• Default model routing — defines the preferred default foundation language model used across agents and workflows unless explicitly overridden by an admin. See Guardrails and allowed models.
• Organization preferences — sets global workspace behavior, including default time zones, notification defaults, and execution telemetry limits.

Setting robust defaults ensures that new employees land immediately in a safe, compliant, and properly configured workspace without requiring manual administrative provisioning.

Roles and administrative permissions

Access to account settings is strictly controlled to maintain system governance:

• Enterprise Admins — responsible for configuring and modifying organization profile data, workspace defaults, and security policies.
• Standard users and team members — manage only their personal account preferences, such as notification delivery or interface themes, while operating strictly within the parameters established by IT admins.

For the full per-role breakdown, see the Capability matrix.

A quick example: zero-touch onboarding

Consider an IT administrator setting up workspace configurations for a growing engineering team:

1. Profile setup — the admin uploads corporate logos, specifies the company name, and aligns workspace branding.
2. Default policy assignment — the admin selects a vetted default language model and sets Enterprise Team Member as the default role for all new invites.
3. Automated onboarding — when fifty new developers join the platform the following week, every user lands in a fully branded environment operating on approved foundation models, with no per-user administrative configuration required.

Account settings overview

Setting category	Core function	Administrative impact
Organization profile	Manages company name, logo, and branding assets	Establishes brand consistency across all workspace tools
Workspace defaults	Sets initial user roles, default models, and preferences	Provides safe, zero-touch onboarding for new team members
Access control	Restricts settings management to Enterprise Admins	Protects global system configurations from unapproved edits

Next steps

• Manage workspace user roles → Capability matrix
• Learn how administrators configure company-wide rules → Governance framework
• Explore model selection and routing controls → Guardrails and allowed models