📖
Typo Help Docs
  • Welcome
  • Getting Started
    • Onboarding
    • Integrations
      • Git
        • GitHub
        • GitLab
        • BitBucket
        • Azure Repos
        • Gitlab On-prem
      • Issue Tracker
        • JIRA
        • Linear
        • GitHub Issue
        • Shortcut
        • ClickUp
      • CI/CD Tool
        • Circle CI
        • Jenkins
        • Heroku
        • GitHub Actions
        • Azure DevOps
        • Custom Deployment Webhook
      • Slack
    • How Requestly setup Typo in a few days
  • Platform
    • Dev Analytics
      • DORA
      • Insights
        • Teams
        • Members
        • Sprints
        • Pull Requests
        • Deployments
      • Incident
      • Goals
      • Investment
      • Initiative
      • WorkLog
      • Custom Reports
      • Settings
        • Teams
        • Member
        • Repository
        • Projects
        • Manage Access
        • Notifications
    • Code Health
      • Code Review
      • Code Coverage
    • DevEx
  • Implementation Plan
    • Phase 1 - Setting Up Data Sources
    • Phase 2 - Metric Configuration
      • Dev360
      • Code Health
      • DevEx
    • Phase 3 - Team Rollout
  • Engineering Metrics
    • DORA
      • Cycle Time
      • Deployment PRs
      • Change Failure Rate
      • Mean Time to Restore
    • Pull Request Metrics
      • Avg. Commits During PR Review
      • Coding Days
      • Coding Time
      • Merge frequency
      • Merge Time
      • Pickup Time
      • PR Size
      • PRs Merged without Review
      • Review Time
      • Efficiency Score
    • Sprint Metrics
      • Carry over
      • Developer Workload
      • Issue Cycle Time
      • Issues At-Risk
      • Scope creep
      • Team Velocity
      • Work Breakup
      • Work Progress
    • Code Quality Metrics
      • OWASP Top 10
      • Vulnerability
      • Security
      • Performance
      • Duplication
      • Code Smell
    • Deployment Metrics
      • Deployment - Failure
      • Deployment - Frequency
      • Time to Build
    • Incident Metrics
      • Incident - Opened
      • Avg Resolution Time
    • DevEx Metrics
      • DevEx Score
      • Space mood
      • Response Rate
      • Manager Support
      • Developer Flow
      • Product Management
      • Development & Releases
      • Culture & Values
  • Configurations
    • Cycle Time
    • Deployment PRs
    • Change Failure Rate (CFR)
    • Mean Time To Restore (MTTR)
    • CI/CD - Deployment
    • Incident
    • Initiative
    • Investment Distribution
    • PR Labels
    • Code Health
    • Code Coverage
    • DevEx
    • Notifications
    • Manage Access
  • FAQ's
    • Data Security
      • GitHub App Permissions Details
      • Why does Typo need write permission to my code?
      • Does Typo has access to my code?
      • What data security guidelines does Typo follow?
    • Integrations
      • Can Typo application work with on-prem Gitlab?
      • How do I get Issue Tracker data?
      • How do I get Git data?
    • Pricing
      • How does the pricing work?
      • How do I upgrade my plan?
    • Access Management
      • My team member is not able to login to Typo
    • Metrics
      • How does Typo predict developer burnout?
      • Is there a way to change the branch that Deployment PRs are measured against?
      • Synchronize “CFR” & “MTTR” without incident management?
      • How quick does the pull-request page update? I closed a PR but the Typo still shows Awaiting Review
      • How do I add any new repo?
      • How to Configure Typo Code Health Checks to Block a PR Merge in Git
      • Can I exclude a person from metrics calculation?
      • Can I track the Cycle time based on the status of the JIRA tickets?
      • How do I unlink the JIRA tracker & integrate Linear?
      • How to exclude a PR from any metric calculation?
      • My data is not visible, I have synced the repo
    • Platform
      • Can I use your application on-premise?
    • Delete Account
      • How can I delete my account?
Powered by GitBook
On this page
  1. Configurations

Manage Access

PreviousNotificationsNextFAQ's

Last updated 3 months ago

Typo offers free access to the Dashboard, where you can assign your team members one of three roles:

Admin:

Full access to all Metrics, Configurations, and Account settings across the entire organization.

Manager:

Access to the team they manage. This role allows users to view all analytics related to their team but does not include account settings.

Developer:

View their activity and DORA insights for the team they are part of.

Below are the details of the access you get based on the different roles -

Dev360
Admin
Manager
Developer

DORA Metric

Yes

Yes, only to their teams.

Yes, only to their teams.

Team Insights

Yes

Yes, only to their teams.

No

Members Insights

Yes

Yes, only to their teams.

Yes, to their own contribution

Sprint Insights

Yes

Yes, only to their teams.Yes

No

Pull Request Insights

Yes

Yes, only to their teams.

Yes, to their own PRs

CI/CD Insights

Yes

No

No

Incidents

Yes

No

No

Worklog

Yes

Yes, only to their teams.

No

Goals

Yes

Yes, only to their teams.

Yes, to their own contribution

Alerts

Yes

Yes, only to their teams.

No

Investment

Yes

Yes, only to their teams.

No

Initiatives

Yes

Yes, only to their teams.

No

Code Health
Admin
Manager
Developer

OverView

Yes

Yes, only to their teams.

No

Repo Issues

Yes

Yes, only to their teams.

No

Pull Request Issues

Yes

Yes, only to their teams.

Yes, to their own PRs

Code Coverage

Yes

Yes

No

Rules

Yes

No

No

DevEx
Admin
Manager
Developer

My Teams

Yes

No

No

Heatmaps

Yes

No

No

Admins and Managers both have access to Settings but with different levels of control. Managers can manage settings specifically for their team, while Admins have access to all configurations across the account.

Granting Access to Users

You can give access to users from the Settings. Follow these steps:

  1. Navigate to Settings > Manage Access.

  2. Click on the Invite User button.

  3. You can invite an existing Git user or a non-Git user.

Inviting a Git User

  1. Click on Yes to invite a Git member.

  2. Select the role: Developer, Manager, or Admin.

  3. Enter the email address where the user will receive login instructions.

By following these steps, you can ensure your team members have the appropriate access to the Typo Dashboard based on their roles and responsibilities.

Inviting a Non - Git User

  1. Click on No to invite a Git member.

  2. Select the desired role

  3. Enter the email address where the user will receive login instructions along with creds.

Users not granted access to the Typo Dashboard using the above steps will be unable to log in and will encounter an error.