Skip to main content

Organization Settings

Overview

Organization settings control the fundamental configuration of your ASCEND deployment. These settings affect how your organization is displayed, how users authenticate, and what security policies are enforced. This guide covers all configurable options and their implications.

Prerequisites

  • org_admin or Super_Admin role
  • Access to Admin Console > Organization tab
  • Understanding of your security requirements

Step-by-Step Guide

Accessing Organization Settings

  1. Log in to ASCEND with administrator credentials
  2. Navigate to Admin Console from the sidebar
  3. Click the "Organization" tab
  4. Settings are displayed in editable form fields

Updating Basic Information

  1. Organization Name

    • Click the name field
    • Enter your organization's display name
    • This appears in:
      • UI header
      • Emails sent to users
      • Reports and exports
      • API responses
  2. Organization Slug (Read-Only)

    • Unique URL identifier
    • Format: lowercase letters, numbers, hyphens
    • Example: acme-corp for https://acme-corp.ascend.ai
    • Cannot be changed after creation
  3. Industry Classification

    • Select from dropdown:
      • Financial Services
      • Healthcare
      • Technology
      • Retail
      • Manufacturing
      • Government
      • Other
    • Used for:
      • Compliance report templates
      • Risk scoring adjustments
      • Industry-specific recommendations

Configuring Contact Information

  1. Primary Contact Email

    • Main administrative contact
    • Receives:
      • System notifications
      • Security alerts
      • Billing communications
  2. Support Email

    • Technical support contact
    • Receives:
      • Technical alerts
      • Integration notifications
      • Error reports

Configuring Security Settings

  1. Require MFA for All Users

    • Toggle checkbox to enable/disable
    • When enabled:
      • All users must configure MFA
      • Login blocked until MFA setup complete
      • Uses TOTP-based authenticators
  2. Enable SSO/SAML

    • Toggle checkbox to enable/disable
    • When enabled:
      • "Sign in with SSO" button appears on login
      • Requires IdP configuration (contact support)
      • Supports SAML 2.0 and OIDC
  3. Session Timeout

    • Enter value in minutes (5-1440)
    • Users automatically logged out after inactivity
    • Recommended values by compliance requirement:
      • PCI-DSS: 15 minutes
      • HIPAA: 15-30 minutes
      • General: 60 minutes

Saving Changes

  1. Review all modified fields
  2. Click "Save Changes" button
  3. Wait for operation to complete
  4. Success toast confirms update
  5. Changes take effect immediately

Configuration Options

Basic Settings

OptionDescriptionDefaultConstraints
nameOrganization display nameSet at onboarding1-255 characters
slugURL identifierAuto-generatedRead-only
domainPrimary domainNot setValid domain format
email_domainsAllowed email domainsNot setArray of domains
industryBusiness sectorNot setPredefined list
primary_emailMain contactAdmin emailValid email
support_emailSupport contactNot setValid email

Security Settings

OptionDescriptionDefaultValues
mfa_requiredEnforce MFAfalsetrue/false
sso_enabledEnable SSOfalsetrue/false
session_timeout_minutesAuto-logout605-1440
cognito_mfa_configurationMFA policyOPTIONALOFF/OPTIONAL/ON
password_policyPassword requirementsCognito defaultObject
allowed_ip_rangesIP allowlistNot setCIDR array

Advanced Settings

OptionDescriptionDefaultAccess
stripe_customer_idBilling identifierAuto-generatedRead-only
cognito_user_pool_idIdentity poolProvisionedRead-only
owner_user_idOrganization ownerFirst adminAdmin only

Domain Configuration

Setting Allowed Email Domains

Restrict user registration to specific email domains:

{
"email_domains": ["acme.com", "acme.io", "acme-corp.com"]
}

Benefits:

  • Prevents unauthorized user invitations
  • Enforces corporate email policy
  • Simplifies user verification

Domain Verification

For SSO and advanced features, domain verification may be required:

  1. Add DNS TXT record provided by ASCEND
  2. Request verification in Admin Console
  3. Verification completes within 24-48 hours
  4. Verified domains appear with checkmark

Timezone Configuration

Configure timezone preferences for your organization:

SettingDescriptionOptions
Display TimezoneTimes shown in UIUser preference or org default
Report TimezoneTimestamps in exportsOrganization setting
Audit Log TimezoneEvent timestampsUTC (stored), converted for display

Available Timezones:

  • America/New_York (Eastern)
  • America/Chicago (Central)
  • America/Denver (Mountain)
  • America/Los_Angeles (Pacific)
  • Europe/London (GMT)
  • Europe/Paris (CET)
  • Asia/Tokyo (JST)
  • Asia/Shanghai (CST)
  • Australia/Sydney (AEST)

API Reference

Get Organization Settings

GET /api/admin/organization
Authorization: Bearer <token>

Update Organization Settings

PATCH /api/admin/organization
Authorization: Bearer <token>
X-CSRF-Token: <csrf_token>
Content-Type: application/json

{
"name": "Acme Corporation",
"domain": "acme.com",
"email_domains": ["acme.com"],
"cognito_mfa_configuration": "ON",
"session_timeout_minutes": 30
}

Response:

{
"success": true,
"message": "Organization updated",
"changes": {
"cognito_mfa_configuration": {
"old": "OPTIONAL",
"new": "ON"
},
"session_timeout_minutes": {
"old": 60,
"new": 30
}
}
}

Best Practices

  1. Complete All Fields

    • Fill in all contact information
    • Set industry classification
    • Configure domain restrictions
  2. Security-First Configuration

    • Enable MFA before adding users
    • Set appropriate session timeouts
    • Configure SSO for enterprise environments
  3. Document Changes

    • Note reasons for configuration changes
    • Export audit logs regularly
    • Maintain change management records
  4. Regular Reviews

    • Review settings quarterly
    • Verify contact information
    • Audit security configurations
  5. Test Before Deployment

    • Test MFA with pilot users
    • Verify SSO configuration thoroughly
    • Confirm session timeout behavior

Compliance Mapping

SettingCompliance StandardRequirement
MFA RequiredPCI-DSS 8.3MFA for remote access
MFA RequiredHIPAA 164.312(d)Unique user identification
Session TimeoutPCI-DSS 8.1.815-minute timeout
Session TimeoutHIPAA 164.312(a)(2)(iii)Automatic logoff
Email DomainsSOC 2 CC6.1Access provisioning
Audit LoggingSOX 302/404Change tracking

Troubleshooting

Settings Not Saving

IssueCauseSolution
Button disabledMissing required fieldComplete all required fields
403 errorInsufficient privilegesVerify admin role
Validation errorInvalid formatCheck field constraints
CSRF errorStale sessionRefresh page and retry

MFA Configuration Issues

IssueCauseSolution
Users not promptedMFA set to OPTIONALChange to ON
Existing users unaffectedAlready authenticatedUsers prompted on next login
TOTP codes failingTime desyncVerify device time

SSO Configuration Issues

IssueCauseSolution
SSO option missingNot enabledToggle SSO in settings
Redirect failsIdP not configuredContact support
Users cannot loginAttribute mappingVerify IdP configuration