Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Adding users to your Runway organization
  • Inviting your team
  • Single Sign-On (SSO, SAML)
  • Integrations

Was this helpful?

  1. Using Runway

Organization settings

PreviousOrganization overviewNextTeam

Last updated 10 months ago

Was this helpful?

Click your organization icon (on the sidebar all the way to the left, second from the bottom) to navigate to the Organization overview, then click the Settings button to the right to view team members, view and manage user groups, and manage SSO settings (if applicable).

Some features may be disabled depending on your user's permissions.

Adding users to your Runway organization

Allowing others to automatically join your organization

When the toggle under Teammates can automatically join your organization is enabled, teammates will be able to join your organization in Runway by visiting and signing up with your approved email domain(s).

If this setting is turned off and a teammate creates a Runway account without an from an existing member of your organization, they will become part of a new, unassociated organization in Runway. If you need assistance moving over teammates from another organization, just .

If you need to add alternate approved email domains to your organization (e.g. your email address is mae@runway.team but your teammate has the address alfred@therunwaycorp.net), please and we'll assist.

Inviting your team

Click the Invite team button to send invites to new team members. When they accept the email invite and create their accounts, they'll be automatically added as members of your existing Runway organization.

Runway does not verify on email addresses for anyone sent an invite by an existing member of an organization.

Single Sign-On (SSO, SAML)

If your organization is configured to use SSO/SAML, you'll see the configuration status here. Organizations on Enterprise tiers can enable this feature by .

Runway uses as an authentication provider for SSO/SAML organizations. Org admins can access the SSO admin portal from here.

Integrations

View all connected integration providers in your organization, and manage provider-level settings like the Runway user groups to Slack groups mapping.

🎛️
🔗
app.runway.team
get in touch
let us know
contacting Runway support
WorkOS
SSO/SAML
invite
allowed domains