Temperstack
Main WebsiteFeaturesPricingBlogAbout usRequest a Demo
  • Overview
    • What is Temperstack?
    • Use Cases
  • User Managment
    • Getting started as Admin
      • Inviting Users
      • Mapping multiple services to a Team
      • Single Sign-On (SSO)
      • Customising ALCOM Audit & scanning
    • Getting Started as a User /Responder
    • Managing profile & contact details
  • Integrations
    • Integrating your Observability tools
      • Setting up AWS Integration
        • Multiple AWS Account Integration
        • IAM Setup Guide
          • Creating IAM User: Temperstack with Policy
          • Creating IAM Role: Temperstack with Policy
      • Setting up Microsoft Azure Integration
        • Creating Access for Temperstack in Azure
      • Setting up Google Cloud Platform Integration
        • Creating Access for Temperstack in GCP
      • Setting up Datadog Integration
        • Creating Access for Temperstack in Datadog
        • Managing resources with Datadog
      • Setting up NewRelic Integration
        • Creating Access for Temperstack in NewRelic
        • Managing resources with New Relic
      • Setting up Splunk Integration
        • Creating Access for Temperstack in Splunk
        • Managing resources with Splunk
      • Setting up Appdynamics Integration
        • Creating Access for Temperstack in Appdynamics
        • Managing resources with Appdynamics
      • Setting up Dynatrace Integration
        • Creating Access for Temperstack in Dynatrace
        • Managing resources with Dynatrace
      • Setting up Oracle Cloud Infrastructure
        • Creating Access for Temperstack in OCI
    • Integrating Custom Alerts & Other Alerting sources
      • Webhook Integration
      • Ingesting Emails as alerts
      • Integrating alert listeners from other observability tools
  • Alert routing & Response Managment
    • On-call scheduling and Escalation Policies
    • Setting up Services
    • Alert notification channels
      • Integrating Slack channels
      • Integrating MS Team
    • Mapping resources to Services
      • Rule based resource to Service Mapping
      • Using AI suggested mapping rules
    • Testing Alerting and Notifications
    • Responding to Alerts
  • Monitoring
    • Setting up and maintaining Comprehensive alerting
      • Alerting Templates- metrics & customisation
      • ALCOM and identifying monitoring gaps
      • Programmatically setting up missing alerts in your Observability tool
      • Alert noise Reduction & Optimisation
  • Uptime Monitoring
    • Real time Availability Monitoring
  • Incident analysis & communication
    • External and Internal service Status Pages
      • Instruction to migrate subscribers from Statuspage
  • AI-Powered Issue Resolution
    • AI powered contextual Runbooks
    • Incident command - alert grouping by incident
    • AI Powered Root cause Identification
  • Reporting & Governance
    • Temperstack Dashboard
    • SLO Dashboard
    • MTTA MTTR
  • Billing & Help
    • FAQs
    • Support
Powered by GitBook
On this page
  • SSO Settings
  • Inviting a new user
  • Creating a new team, adding users & mapping services to teams
  • Allow list of services for AWS (Organization scan)
  • Manage your Profile
  • Accepting invite as a new user
  1. User Managment
  2. Getting started as Admin

Single Sign-On (SSO)

Last updated 4 months ago


SSO Settings

The Google Single Sign-On (SSO) setting in Temperstack provides administrators with the ability to control and secure user access by restricting which email domains can use Google SSO for logging in. This feature ensures that only users from specific, authorized domains are allowed to access Temperstack through Google SSO, thereby enhancing security and control over user access.

Setting Up Google SSO in Temperstack

To set up Google Single Sign-On (SSO) in Temperstack and apply email domain restrictions, follow these steps:

  1. Log in to the Dashboard

  1. Navigate to Admin

  2. Within the Admin section, select Manage Organization.

  1. Scroll to Login Email Domain Restriction:

  2. Enter Allowed Email Domains: In the provided field, enter the email domain(s) you want to allow for Google SSO login. Separate multiple domains with commas (e.g., yourcompany.com, partners.com).

  3. Enable Domain Restriction: Check the option Only Allow SSO Login to enforce that only users from the specified email domains can log in using Google SSO.

  • Existing Users: Users from other email domains who are already part of Temperstack will not face any new restrictions. They can continue to log in using their existing methods.

  • Default Setting: If no email domains are entered, Google SSO will be open to all email domains by default.


Inviting a new user

  1. Navigate to Admin -> Manage Organization -> User Management.

  2. To invite users, fill in the mandatory details, including:

    • Name

    • Email ID

    • Role

    • Country code

  3. Once the user accepts the invite, they will appear in the list below.

  4. In the user list, you can:

    • Change the user’s role

    • Delete the user


Creating a new team, adding users & mapping services to teams

  1. Navigate to Admin -> Manage Organization -> Team Management.

  2. Create a team by entering a name and clicking the creation button.

  3. Once created, you can:

    • Add team members.

    • Map services to the team.

    • Delete the team if it is no longer needed, which helps in organizing and monitoring your organization effectively.

  4. After creating a team, you can edit it at any time to:

    • Add more members.

    • Map additional services as needed.


Allow list of services for AWS (Organization scan)

To perform an organizational scan in TemperStack:

  1. Navigate to Admin and select Manage Organization.

  2. Within Manage Organization, locate and select Organization Scan.

  3. In TemperStack, we provide a wide range of integrations with various AWS services such as EC2, SQS, RDS, ElastiCache, Lambda, and more.

  4. When conducting an organizational scan, you can customize the scan according to your requirements by enabling or disabling specific integrations.

  5. For example, if you wish to scan only AWS SQS resources, access "Manage Organization" in "Admin" and disable all other services except SQS.

  6. This approach ensures that the scan focuses solely on fetching and displaying information pertaining to SQS resources.


Manage your Profile

  1. Navigate to Admin -> Profile.

  2. Click on the "Edit" icon next to your name to modify it, then click "Update" to save the changes.

  3. Update your phone number by entering the new number in the designated field, then click "Update" to save.

  4. To change your password, click on the "Change Password" option, enter your current password followed by the new password, then click "Update Password" to confirm the change.

Enabling Two-Factor Authentication

For enhanced security, you can enable Two-Factor Authentication (2FA) by using the toggle button provided below. This feature adds an extra layer of protection to your account.


Accepting invite as a new user

  1. After inviting a new user, an invitation email is sent to the user's provided official email address.

  2. The user receives the invitation email and accepts it.

  3. Upon acceptance, the user is successfully added to the team.

Only Admins can send invites to new users.

SSO Settings
Dashboard
Admin > Manage Organization
SSO
User Management
Team Management
Organization Scan
Profile