+ Note that your GitKraken account is not compatible with Git Integration for Jira.
-It is recommended to create and use a single GitKraken account for yourself, to not create a second account for yourself, and to not share an account with others.
+Note that your GitKraken account is not compatible with Git Integration for Jira.
+We recommend using a single GitKraken account for yourself. Avoid creating duplicate accounts or sharing your account with others.
+**Other options:**
+- Google
+- Microsoft
+- Email + password
+- [Single Sign-On (SSO)](/gk-dev/gk-dev-single-sign-on/)
-Once you have created your GitKraken account, your account is tied to the primary email address of whichever method you selected. If you use the “Sign up with Email” method, you will need to verify your email address with a link sent to your email.
+Each login method is tied to your primary email address. If you sign up with email, you’ll need to verify it via a confirmation link.
+
+
+ 
+
+ GitKraken is GDPR-compliant and this action cannot be undone. This action will revoke access to all GitKraken products and services linked to your account.
+This Feature is only available for Pro subscription tiers or higher
+This feature is only available on Pro subscription tiers or higher. See pricing options.
- Note: - Currently, Automations supports cloud integrations. Self-Hosted Integration Automations will be available at a later date. -
+Note: Automations currently supports cloud integrations. Self-hosted support will be added in a future update.
+
+ 
+
+ - Note: - A webhook will be set up on the selected repository after saving the automation. You will need to have permission on the repository to allow the creation of the webhook. -
+Note: Creating an automation sets up a webhook on the repository. You’ll need the appropriate permissions.
+- **Pull request content**
+ Trigger on PR metadata, activity, or discussion.
+
+- **Review: Status**
+ Watch for approvals, missing reviews, or stale feedback.
+
+- **Branch and origin**
+ Trigger based on the source or target branch, or the repository.
+
+- **CI/CD checks**
+ React to build, test, and deployment outcomes.
+
+- **File condition**
+ Match file paths, folders, or specific code snippets.
+
+- **GitKraken AI**
+ Analyze pull request diffs and metadata to detect conditions you care about.
+
+
+ 
+
+ - Note: - A file path is different from a file name. For example: *src/app/index.ts* is a file path, while *index.ts* is a file name. -
+Note: A file path includes folders, e.g. src/app/index.ts, while a file name is just index.ts.
- Note: - A pull request can never have the author of the pull request as a reviewer. If an action would cause the author to be a reviewer on their own pull request, GitKraken will skip over that step, but still perform all other steps on the Action. -
+Note: Authors can’t review their own PRs. If selected, GitKraken will skip that step and apply all others.
+
+ 
+
+### Sort automations
+Sort by **Status** (enabled/disabled) or **Action** (type of triggered automation).
-### Sort Automations
+
+
+Click again from the list view.
+***
-### Add Additional Automations
+## Repository management
-To create an additional Automation, select .
+The Repository Management screen shows which repos have active automations, who created them, the provider, and automation counts.
-## Repoistory Management
+
+
+
+
+## Next Steps
+Explore more ways to automate and streamline Git workflows:
+- [Connect an Integration](/gk-dev/gk-dev-integrations/)
+- [Use Launchpad to manage PRs and issues](/gk-dev/gk-dev-home/#launchpad-your-daily-git-dashboard)
+- [Visualize metrics with GitKraken Insights](/gk-dev/gk-dev-insights/)
+- [Return to GitKraken.dev Support Home](/gk-dev/gk-dev-home/)
\ No newline at end of file
diff --git a/gk-dev/gk-dev-dashboard-management.md b/gk-dev/gk-dev-dashboard-management.md
new file mode 100644
index 0000000..12a6ca4
--- /dev/null
+++ b/gk-dev/gk-dev-dashboard-management.md
@@ -0,0 +1,279 @@
+---
+title: Dashboard Management in GitKraken Insights
+description: Learn how to add and interpret key DORA and Pull Request metrics, arrange your layout, and use filters to analyze data on dashboards.
+taxonomy:
+ category: gk-dev
+---
+Last updated: December 2025
+
+
+## Overview
+
+GitKraken Insights brings your Git data, pull requests, issues, and CI/CD results into one place. Instead of juggling tools or exporting spreadsheets, you get dashboards that show how work is really moving across code, reviews, and releases. The goal is to give both devs and leads a clear view of progress and bottlenecks without extra reporting overhead.
+
+### Key benefits
+
+- **In your workflow:** Metrics come straight from the tools you already use: Git, PRs, CI/CD, issue trackers. No duplicate work, no disruption.
+- **Useful context:** See how code changes connect to tickets, review quality, and team goals. Less vanity stats, more signal.
+- **Clear next steps:** Spot inefficiencies and get practical ways to improve, whether it’s review speed, investment in features vs. fixes, or build times.
+
+---
+
+## Adding Metrics
+
+Before you can add metrics, complete these setup steps:
+
+1. [Request a guided tour to get access](https://www.gitkraken.com/insights#form).
+2. Connect GitKraken Insights to your GitHub account.
+3. Wait for your repositories to finish importing. For detailed instructions, see the [Getting Started guide](https://help.gitkraken.com/gk-dev/gk-dev-insights).
+
+Once setup is complete, open the **Insights > Dashboard** tab from [gitkraken.dev](https://gitkraken.dev).
+
+
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 🚨Important: Once you get the pack, you must sign into your GitKraken account through GitHub one more time to enable Pro on your account. -
-
-
-Or you may login by navigating to the profile dropdown Sign into a Different Account Sign in with GitHub
-
-
-
-
-
-When you sign in with GitHub, GitKraken Desktop will check whether your GitHub account has the GitHub Student Pack. If the app sees the pack, you should see the `Pro` flag in the bottom right of the UI and you will be able to open private repos.
-
-If you don't see `Pro` then this means GitKraken does not see a pack with the email address tied to your GitHub account. This may mean you need to update the primary email address for your GitHub.com account.
-
-***
-
-## Student Pack FAQ
-
-### How long does it take to approve the GitHub Student Pack?
-
-GitHub controls the approval process for the GitHub Student Pack. If you have questions about the status of your application, please email education@github.com.
-
-Once you get approved, all you need to do is sign into your GitKraken account with your GitHub account 1 more time.
-
-### I got the student pack but I don't see Pro when I open GitKraken. What should I do?
-
-Once GitHub has approved your pack, you must sign into your GitKraken account through GitHub 1 more time to enable Pro.
-
-If you are still not seeing Pro, sign out of GitHub.com in your default browser. Next, in GitKraken, go to `File > Sign in to a different account > Sign in with GitHub`
-
-
-
-Lastly, log into your GitHub.com account using the email address that has the GitHub Pack.
-
-
-
-Once authorized, you can go back to GitKraken, and you should see `PRO` in the lower right-hand corner. If you continue not seeing `PRO`, you must confirm with GitHub that you still have the student pack. They can be reached at education@github.com.
-
-### How long will I have Pro as a student or teacher?
-
-You will have Pro while you have an active GitHub Student Pack. Once the pack expires, your GitKraken Pro access will expire too.
-
-### Can I use my GitKraken Pro license on more than one computer?
-
-Yes, your GitKraken subscription is associated with your email address, not a specific computer. So you can use GitKraken Desktop on as many computers as you'd like!
-
-### How do I reverify my GitHub Student Developer Pack?
-
-To verify or reverify your GitHub Student Developer Pack, sign into GitKraken using GitHub again. Follow the instructions outlined [here](gk-dev/gk-dev-edu-pack/#i-got-the-student-pack-but-i-dont-see-pro-when-i-open-gitkraken-what-should-i-do).
-
-### How do I report a bug or vulnerability?
-
-To report a bug, join our [Public Slack](https://www.gitkraken.com/join-slack-community) and report the issue in any channel. Make sure to @keif in your report or you can send Keif a direct message.
-
-To report a Security vulnerability, please email security@gitkraken.com.
-
-### How do I submit a request related to my rights under GDPR?
-
-If your team needs all account data deleted permanently upon cancellation, please email compliance@gitkraken.com with such requests. Please note, deletion of data is irreversible.
-
-### I have a question about purchasing GitKraken.
-
-Please reach out to our [Success team](https://www.gitkraken.com/sales-inquiries) for any questions regarding purchasing.
-
diff --git a/gk-dev/gk-dev-faq.md b/gk-dev/gk-dev-faq.md
index 9f7093d..d191ace 100644
--- a/gk-dev/gk-dev-faq.md
+++ b/gk-dev/gk-dev-faq.md
@@ -4,85 +4,93 @@ title: GitKraken Accounts and Licenses FAQ
description: Here are the most common questions about GitKraken accounts and licenses.
taxonomy:
category: gk-dev
-
+
---
+Last updated: June 2025
+
### GitKraken automatically put me in a trial. Is there a way to use the app without the trial?
-All new GitKraken accounts will automatically get a GitKraken trial of all paid client features.
+All new GitKraken accounts automatically begin a 14-day trial of all paid features.
-If you plan to use the free version, the trial will automatically end after 7 days and the app will change to the free version.
+If you plan to use the free version, simply let the trial expire—GitKraken will revert to the free plan.
-If you have questions about your trial, please [contact our sales team](https://www.gitkraken.com/sales-inquiries).
+If you have questions, please [contact our sales team](https://www.gitkraken.com/sales-inquiries).
***
-### I just subscribed but I still fee FREE in the lower right corner.
+### I just subscribed but I still see FREE in the lower right corner.
+
+Make sure you’re logged in with the same email address tied to your paid subscription.
-Be sure you are logged in with the same email address registered with your paid GitKraken subscription. You can check by navigating to Sign into a different account, and then verify that your email is correct.
+To check, navigate to:
+ Sign into a different account
***
### Can I transfer account ownership?
-Yes. If you are the `Owner` of a Paid subscription, then you may [transfer ownership](/gk-dev/gk-dev-organization/#transfer-ownership) to a different user on your account from [gitkraken.dev/settings/organization](https://gitkraken.dev/settings/organization).
+Yes. If you're the `Owner` of a Paid subscription, you can [transfer ownership](/gk-dev/gk-dev-organization/#transfer-ownership) to another user from [gitkraken.dev/settings/organization](https://gitkraken.dev/settings/?source=help_center&product=gitkraken_dot_dev).
-
+
+ 
+GitKraken.dev is a browser-based Git project management app. From tracking issues and pull requests to organizing repositories with your team, GitKraken.dev helps you stay productive directly from your browser.
+
+
+ This Feature is only available for Pro subscription tiers or higher
-
+This feature is only available on Pro or higher plans. See pricing options.
+
+
+ 
+
+ 
+
+ This Feature is only available for Pro subscription tiers or higher
+This feature is only available on Pro or higher plans. See pricing options.
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ This Feature is only available for Pro subscription tiers or higher
+This feature is only available on Pro or higher plans. See pricing options.
+
+ 
+
+ 
+ 
+ A member of the GitKraken team will contact you right away to walk you through Insights and explain how to enable access for your organization.
-This Feature is only available for Pro subscription tiers or higher
-- Note: Insights is in Preview mode, and we'd love to hear your thoughts and feedback. Just click on the "Feedback" button in the top right to tell us what you think. -
-
+
+ - When using Insights, we will attempt to add webhooks to your workspace repositories in order to reduce API calls and improve data performance. -
-- Filtering by 14 days is available for Teams subscriptions and filtering by 28 days is available for Enterprise Subscriptions. -
-
+ 
+ 
+ 
+- Expect **past month’s activity** to appear within a few hours.
+- Full **year’s activity** is usually ready within one to two days.
+- Track import progress anytime from the **Dashboard** tab.
-- Note: Exporting is only available for Enterprise subscriptions. -
-
+ 
+1. Under **Add Integration**, select your self-hosted service (e.g., GitHub Enterprise).
+2. Enter the Host Domain.
+3. Click **Generate a token on {service}**.
+ - This opens a pre-filled Personal Access Token (PAT) creation page.
+4. Create the PAT.
+5. Paste the token into GitKraken.
+6. Click **Connect**.
+
+
+ Note for GitHub.com: In order to work with repositories owned by a GitHub organization, the organization will need to allow Organization Approval for GitKraken.
-To access repositories owned by a GitHub organization, organization approval is required. Request organization approval.
+ + +*** + +## What’s Next? + +Once connected, you can: +- Use [Launchpad](/gk-dev/gk-dev-home/#launchpad-your-daily-git-dashboard) to track PRs and issues. +- Organize repos into [Workspaces](/gk-dev/gk-dev-home/#workspaces-organize-projects-by-team). +- Share [Cloud Patches](/gk-dev/gk-dev-home/#create-and-share-cloud-patches). + +Return to the [GitKraken.dev Support Home](/gk-dev/gk-dev-home/) to explore more features. diff --git a/gk-dev/gk-dev-organization.md b/gk-dev/gk-dev-organization.md index 9098273..587c4bb 100644 --- a/gk-dev/gk-dev-organization.md +++ b/gk-dev/gk-dev-organization.md @@ -1,79 +1,29 @@ --- - -title: Manage GitKraken Organization -description: Learn about GitKraken Organizations +title: Manage GitKraken Organizations | Roles, Users, Teams, SSO +description: Learn how to manage GitKraken organizations, assign roles, add users, configure teams, and set up SSO. taxonomy: category: gk-dev - --- -A GitKraken organization is a collection of [GitKraken accounts](/gk-dev/gk-dev-account/) which unlocks a shared [subscription](/gk-dev/gk-dev-subscription/), collaboration features between members, and administration of the members in the organization. If you are creating an account for the first time, an organization will automatically be created for you. -Community users are a single user plan, and can not perform any org management. Pro plans and above can perform Org management functions.
-
+Last updated: June 2025
-Here you can enter as many email addresses as you want and the [role](/gk-dev/gk-dev-organization/#roles) (in the drop down) you would like to assign them all.
-
-
-
-Only members that have a [role](/gk-dev/gk-dev-organization/#roles) with permission can add users to an organization. When you do add someone, it will consume a license of your subscription. If all available licenses are consumed when adding a user, a billing summary will show up during the process, select "Purchase" to complete the transaction and add the users.
-
-
-
-You can also add licenses in bulk to your organization separately from adding users by going to the [Subscription](/gk-dev/gk-dev-subscription/) section in your organization.
-
-***
-
-## Inviting users to your organization
+Create an organization in GitKraken.dev to manage your team’s access, roles, licenses, and SSO. Centralize your GitKraken [subscription](/gk-dev/gk-dev-subscription/) to simplify provisioning and oversight across all GitKraken products.
-As a User, you have the ability to invite other users to the organization for an Owner, Admin, or Billing Contact to approve and/or purchase a license for.
-
-To invite a user, navigate to gitkraken.dev > Users > Invite Users. Then provide the email(s) of the desired user(s).
-
-
-
-This will send an email to any Owner, Admin, or Billing Contact to review the invited user. They can select `Review` on the email or see the invitees from gitkraken.dev > Users > Review. Here, they can Approve or Deny the user. If your organization is at its user limit, you will be prompted to purchase an additional license when approving.
-
-
-
-***
-
-## Reallocate licenses
-
-Any Owner, Admin, or Billing Contact may remove users and then add users to reallocate licenses.
-
-The Billing Contact role cannot remove or edit Owner or Admin users.
-
-To reallocate a license, navigate to Users and then select "Remove" for the desired user. Then, you can add the new user.
-
-***
-
-## Import and export users
-
-To import multiple users via CSV select the “Add User” button. From here you can select “Import via CSV”. When importing users, be sure to have columns for `Email`, `Username`, `Role`, `User License`.
-
-
-
-To export users to a CSV, select “Export via CSV”. The export will contain columns for Email, Username, Role, User License.
-
-
+Community users are on a single-user plan and cannot perform any organization management. Pro plans and higher can manage users, roles, teams, and settings.
+| Permission | Owner | Admin | +Lead | User | Billing Contact | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Licensed to use GitKraken | +Licensed to use paid GitKraken features | +✅ | ✅ | ✅ | ✅ | @@ -98,13 +50,15 @@ Roles grant members permissions within an organization. There are four roles a u✅ | ✅ | + | ✅ | |
| Create and manage teams | ✅ | ✅ | -+ | ✅ | +✅ | ✅ | ||||
| ✅ | ✅ | + | ✅ | |||||||
| + | + | |||||||||
| Connect data sources to GitKraken Insights | +✅ | +✅ | ++ | + | + | |||||
| Access and manage GitKraken Insights | +✅ | +✅ | +✅ | ++ | + | |||||
| Assign and manage Insights licenses | +✅ | +✅ | +✅ | ++ |
+
+
+
+
+
+
+ 
+
+ 
+- Organization name
+- Ownership
+- SSO setup
+- Organization membership
+
+
+
+> **Note:** Ownership transfers are final unless the new owner reassigns it.
+
+
+ 
+Leaving an organization will revoke your GitKraken license and access to shared collaboration features.
+
+
+ If you make GitKraken purchases for multiple customers and already have a GitKraken account, choose to sign into an existing account and continue onto Step 2.
+If you already use GitKraken for multiple customers, simply log in to your existing account and continue to Step 2.
-
-Once you have created your GitKraken account, your account is tied to the primary email address of whichever method you selected. If you use the email method, you will need to verify your email address with a link sent to your email.
+
+ If you need to make a new organization for a separate customer, you can do so at gitkraken.dev/purchase.
+To create a new organization for a different customer, visit gitkraken.dev/purchase.
+
+ GitKraken Subscriptions only accept card, PayPal, ACH bank payments, and Google Pay. However, invoicing is supported for large purchases of GitKraken Enterprise. Contact our Customer Success team to learn more.
+We accept card, PayPal, ACH, and Google Pay. Invoicing is available for large GitKraken Enterprise orders. Contact our Customer Success team for invoicing support.
The cost to add users to an existing account is prorated against the billing cycle of the initial purchase of the account.
-If you are a reseller and the customer’s organization is not listed on your GitKraken account, contact our Customer Success team for assistance.
+License costs are prorated against the original billing cycle. If a customer org is not listed under your account, contact our Customer Success team.
+ 
+ + Providers marked with an asterisk (*) support setting a custom API key and URL. +
++ These settings apply across all GitKraken products used by your organization. +
+
+ + GitKraken encrypts all Cloud Patches, even when self-hosted. Only users with access to the patch link and repository permissions can view contents. +
+
+- [Learn how to use Cloud Patches](/gk-dev/gk-dev-home/#cloud-patches-pro)
+- [Manage Org Roles](/gk-dev/gk-dev-organization/#roles)
+- [Explore GitKraken.dev Support Home](/gk-dev/gk-dev-home/)
diff --git a/gk-dev/gk-dev-security.md b/gk-dev/gk-dev-security.md
index c33aeca..0e9cb36 100644
--- a/gk-dev/gk-dev-security.md
+++ b/gk-dev/gk-dev-security.md
@@ -1,13 +1,15 @@
---
-
-title: Security Information for gitkraken.dev
-description: Data Security Information for gitkraken.dev
+title: Security Information for GitKraken.dev
+description: Learn how GitKraken.dev encrypts data in transit and at rest across features like Workspaces, Launchpad, and Cloud Patches.
taxonomy:
category: gk-dev
-
---
-Below is a chart outlining some basic security information regarding the type of data that we collect and how we store it.
+Last updated: June 2025
+
+## Information Collection/Storage
+This page outlines how GitKraken.dev handles data security—including what data we collect, how it's transmitted, where it's stored, and how it's protected at rest.
+
| Service | What information are we collecting | How is this information secured in the transfer| Where is this information stored | How is this information secured in storage |
| --- | --- | --- | --- | --- |
@@ -16,3 +18,17 @@ Below is a chart outlining some basic security information regarding the type of
| Subscriptions | Billing info: lastFour, name, type (credit card, paypal, ach...), zip, country, creditCard type (mastercard, visa...) | Encrypted with TLS | MongoDB Atlas | Encrypted at rest (AES-256) |
| Launchpad | Storing meta-data for issues/pull-requests/URLs | Encrypted with TLS | Postgres (RDS) | Encrypted at rest (AES-256) |
| Cloud Patches | Info related to the patch (repo name/URL/provider/base branch name/etc.) + the patch content itself. | Encrypted with TLS | Patch info is stored in a Postgres database, patch content is stored in AWS S3. | SSE-S3, which uses 256-bit Advanced Encryption Standard (AES-256) |
+
+## SOC2
+Gitkraken and it’s tools are now SOC 2 Certified! If you would like to request a copy of our SOC2 report, please visit our [Trust Center](https://trust.gitkraken.com/) to get the request process started. Please note that in order to provide a copy of the report, we will need you to sign an MNDA.
+
+This Feature is only available for Pro subscription tiers or higher
+SSO is available with a GitKraken Advanced or Enterprise subscription. It’s also included in the 30-day multi-user trial.
+
+Here are some important terms related to SSO:
-The above diagram depicts what a typical SSO setup entails. Here is some relevant terminology:
+**Directory Server:** A directory server stores information about organizational “objects” such as printers, computers, shared folders, users, or groups. These objects may be organized hierarchically.
-**Directory Server:** A Directory Server is an application that stores information about the “objects” that belong to an organization. An object is typically something like: printers, computers, shared folders, users, or groups. Some objects can contain other objects which then allows them to reflect hierarchical structures.
+Examples:
+* Microsoft Active Directory
+* Oracle Identity Governance (OIG) Suite
+* JumpCloud
-Examples of Directory Server applications are:
-* Microsoft Active Directory
-* Oracle Identity Governance (OIG) Suite
-* Jump Cloud
+**Identity Provider (IdP):** An IdP manages identity information and provides authentication services. It stores users, groups, and apps that rely on it to authenticate logins.
-**Identity Provider:** An identity provider (abbreviated IdP or IDP) is a system entity that creates, maintains, and manages identity information as well as provides authentication services to relying applications within a distributed network. An IdP provider stores 3 main components: Users, Groups, and Applications.
-
-Examples of Identity Provider applications are:
-* Azure Active Directory
+Examples:
+* Azure Active Directory
* Okta
* Google Identity Platform
-The Identity Providers provide services that allow third party applications to authenticate their users. The authentication mechanism they provide is called “Oauth”, which allows third party applications to authenticate users without accessing/storing their password.
+Identity providers authenticate users on behalf of other apps, using a protocol called **OAuth**. This ensures the third-party apps can verify a user without needing access to their password.
-**Third party applications:** These are the applications that use IdP services to authenticate users. The end user is redirected to the IdP to instead login there. Then the Idp directs back to the 3rd party app to complete the login, confirming that the user is who they claim to be.
+**Third-party applications:** These are the services that use an IdP to authenticate users. Users are redirected to the IdP to log in, then returned to the application once verified.
-Examples of third party apps:
-* GitKraken
-* Slack
-* Jira
+Examples:
+* GitKraken
+* Slack
+* Jira
***
-## SSO in GitKraken
+## How SSO works in GitKraken
-GitKraken is a 3rd party application in this scenario. The owner or an admin of the GitKraken organization can set up SSO with GitKraken.
+GitKraken is a third-party application in this context. The Owner or an Admin of a GitKraken organization can set up SSO.
### Supported Identity Providers
-GitKraken uses SAML 2.0 for SSO, therefore any IdP that supports SAML 2.0 should work with GitKraken.
+GitKraken supports SAML 2.0 for SSO. Any identity provider (IdP) that supports SAML 2.0 is compatible.
### License Requirements
-Single sign-on requires a GitKraken Teams, GitKraken Enterprise, or a 30-day multi-user trial. To use multiple domains requires GitKraken Enterprise or a 30-day multi-user trial.
+SSO requires a GitKraken Teams or Enterprise subscription, or a 30-day multi-user trial. To support multiple domains, GitKraken Enterprise or the multi-user trial is required.
+
+### SSO Enforcement in GitKraken
-### SSO Enforcement on GitKraken
+- SSO is enforced at the **domain level**:
+ - Users whose account emails match a verified SSO domain must log in via SSO.
+ - Owners and Admins can log in using any method.
-- GitKraken SSO is enforced at the domain level. This means every account on GitKraken that has an email for the account which matches the domain is required to login using SSO.
- - Only users with the user or billing contact role are required to use SSO. The Owner and admins of the organization can login using any method of choice.
-- SSO is also enforced by the organization. This means that all users that match the domain must be a part of the organization to login.
- - This also means that all members in the organization must match one of your SSO domains. Before turning on SSO, all non-matching users must be removed from the organization.
-- Accounts belong to the domain and organization. When SSO is enabled:
- - Users cannot create additional organizations or subscriptions.
- - Accounts cannot self-leave the organization
- - Users cannot change their account email or password.
- - Existing accounts that already have additional organizations or subscriptions will still have them.
- - Existing accounts cannot access their additional organizations or subscriptions until they can login using SSO and are a part of the organization.
+- SSO is also enforced at the **organization level**:
+ - All users matching a verified domain must be part of the GitKraken organization.
+ - Users with unmatched domains must be removed before SSO can be enabled.
+
+- Additional rules:
+ - Users cannot create other organizations or subscriptions.
+ - Users cannot leave the organization or change their email/password.
+ - Existing accounts with other organizations/subscriptions can keep them, but can’t access them until they are part of the organization and sign in with SSO.
### Just-in-time provisioning (JIT)
-You can enable JIT on GitKraken.dev > Settings > SSO. With JIT enabled, when a user logs in with SSO successfully and is not part of your organization, they will automatically join your organization and consume a license. You do need to have spare licenses available for this to work, if all licenses are used then the user will not join automatically even if JIT is on.
+JIT can be enabled at GitKraken.dev > Settings > SSO. When JIT is active and a user logs in successfully via SSO, they will automatically join the organization and consume a license.
+
+Note: JIT only works if there are available licenses. If none are available, users will not be added.
### SSO login experience
-- To login with SSO, click “SSO” on the login page.
-- When a user that belongs to your domain logs in using anything but SSO, they will see a message explaining they need to login using SSO.
-- When a user logs in using SSO successfully but is not a part of the organization, they will receive a message telling them to contact their admin to join the GitKraken organization.
-- The owner and admins of the organization can log in using any method.
+- On the login screen, select **SSO** to sign in.
+- If a user tries to log in using a method other than SSO and matches a managed domain, they’ll see a message requiring SSO.
+- If a user logs in with SSO but is not part of the organization, they’ll be prompted to contact an admin.
+- Owners and Admins may sign in using any supported method.
+Gitkraken SSO does not support signing in through the Identity Provider's dashboard.
+
-
-3. Click on *Add app*.
-
-
-
-4. Click *Add custom SAML app*.
-
-
-
-5. Type in your app name (such as GitKraken SSO).
-
-
-
-6. Copy your *SSO URL* and *Certificate*.
-
-
-
-7. Enter the callback URL `https://api.gitkraken.com/oauth/sso/callback` for *ACS URL* and *Entity ID*.
-
-
-
-8. Add desired attributes and click on *Finish*.
-
-
-
-9. Click on *TEST SAML LOGIN*.
-
-
-
-10. Click on *ALLOW ACCESS*.
-
-
-
-11. Select *ON for everyone* and save.
-
-
-
-Now you are all set to [setup your SSO on a GitKraken Organization](/gk-dev/gk-dev-single-sign-on/#setup-sso)
+2. Click on Apps and then Web and mobile apps.
+
+
+
+
+
+ https://api.gitkraken.com/oauth/sso/callback for both ACS URL and Entity ID.
+
+
+
+
+
+ 
+
5. Click on *New application* from the top of the page.
-
+
6. Select *Create your own application*.
-
+
7. Give your application name (such as "GitKraken SSO") and select "Integrate any other application you don't find in the gallery (Non-gallery)".
-
+
8. Select *Single sign-on* from the left sidebar and then choose *SAML*.
-
+
9. Click the edit icon in the top right corner to configure SAML.
-
+
10. Input the *Entity ID* URI and *Reply URL*. Both of these should direct to `https://api.gitkraken.com/oauth/sso/callback` for GitKraken SSO.
-
+
Now you are all set to [setup your SSO on a GitKraken Organization](/gk-dev/gk-dev-single-sign-on/#setup-sso)
### Okta
@@ -226,32 +241,32 @@ How to Create SAML Application in Okta:
2. Enter your Okta credentials and login.
3. Go to admin dashboard and select *Applications* in navigation bar.
-
+
4. Click on *Add Application*.
5. Select *Create New App*.
-
+
6. Select *SAML 2.0* as a Sign on Method and click to next button.
-
+
7. Enter a name of application (such as "GitKraken SSO").
-
+
8. Configure SAML Integration. The *Single sign on URL* and *Audience URI* fields should direct to `https://api.gitkraken.com/oauth/sso/callback`.
-
+
Step 9: Scroll down to the attribute statement and fill in the optional fields.
-
+
Step 10: Select “I am an Okta customer adding an internal app” from option menu and then click to finish.
-
+
Now you are all set to [setup your SSO on a GitKraken Organization](/gk-dev/gk-dev-single-sign-on/#setup-sso)
@@ -265,79 +280,79 @@ How to Create SAML Application in Ping Identity
3. Go to the home page and click on *Add Environment*.
-
+
4. Select the appropriate solution based on your need (in this guide, we use *Customer solution*) and click *Next*.
-
+
5. Select *PingOne SSO*, then click *Next*.
-
+
6. Type in your environment name (in *TRIAL ENVIRONMENT NAME*), then click *Finish*. Now your environment is created. Go ahead and click on it.
-
-
+
+
7. Select Identities to add some users. Once you are done adding them click on Groups, and then click on the plus button to add a group. (Make sure to add users with their email addresses).
-
-
+
+
8. Select *Groups*, then click on the plus button to add a group. Once you have that, you can add the users to your group.
-
+
9. Select *Connections*.
-
+
10. Click on the plus button.
-
+
11. Enter a name for your application, then select *SAML Application*. Next click on the *Configure* button which appears once you select your application type.
-
+
12. Select *Manually Enter*. Type in the URL for *ACS URLs* and *Entity ID*, then click on *Save*.
(URL: `https://api.gitkraken.com/oauth/sso/callback`)
-
+
13. Click on the toggle button so the users would have access to your application.
-
+
14. Click on *Attributes* then add email as your new attribute.
-
-
+
+
15. Time to add the group we created in Step 8.
-
+
16. Select the pencil icon pictured below.
-
+
17. Click on the plus icon to add the group, then click on *Save*.
-
-
+
+
18. Go to the *Configuration* tab to copy your *IDP Metadata URL* and download your metadata (*Download Metadata* button).
-
+
-19. Log into gitkraken.dev/settings/sso and select "Setup SSO". Type in your Connection name and Domain.
+19. Log into gitkraken.dev/settings/sso and select "Setup SSO". Type in your Connection name and Domain.
20. Then use the *IDP Metadata URL* and *Metadata* from step 18 for *Metadata URL* and *Metadata*. Click on *Create Connection*
-
+
21. Now the users who were added in step 7 can *Sign in with SSO*.
diff --git a/gk-dev/gk-dev-student-pack.md b/gk-dev/gk-dev-student-pack.md
new file mode 100644
index 0000000..43b9e6c
--- /dev/null
+++ b/gk-dev/gk-dev-student-pack.md
@@ -0,0 +1,39 @@
+---
+title: GitKraken Student Pack
+description: Get a free GitKraken subscription for students.
+taxonomy:
+ category: gk-dev
+---
+
+Last updated: August 2025
+
+GitKraken offers a free Student Pack for students to use GitKraken Desktop, GitLens, CLI, and GitKraken.dev.
+
+This plan is a 6 month free trial of PRO features for students who are verified on Github Student Developer Pack.
+
+After the 6 month free trial, you can upgrade to a PRO subscription at a discounted rate.
+
+# What is in the GitKraken Student Pack
+
+- GitKraken Desktop
+- GitLens
+- GitKraken CLI
+- GitKraken.dev
+
+# How to get the Student Pack
+
+1. You need to be a student with a valid student email address and a verified Github Student Developer Pack.
+2. Create a new account on GitKraken using your Github account.
+3. Once you have created your account, the `Student`flag shows next to your name in GitKraken.dev
+4. Now you can sign into all GitKraken products with your Github account with premium features applied.
+
+
+
+# How to upgrade to a PRO subscription
+
+When the 6 month free trial is about to end, you will be notified both in the app and in the email you used to sign up.
+
+
+
+You can upgrade to a PRO subscription at a discounted rate following the instructions in the email. In the checkout process, verify the discount code is applied.
+
diff --git a/gk-dev/gk-dev-subscription.md b/gk-dev/gk-dev-subscription.md
index 42a4595..684e7bb 100644
--- a/gk-dev/gk-dev-subscription.md
+++ b/gk-dev/gk-dev-subscription.md
@@ -1,64 +1,136 @@
---
-
-title: Manage GitKraken Subscriptions
-description: Learn about GitKraken Subscriptions
+title: Manage GitKraken Subscription and Billing
+description: Purchase or cancel GitKraken subscriptions, update billing info, and download past invoices.
taxonomy:
category: gk-dev
-
---
-Subscriptions are tied directly to an [organization](/gk-dev/gk-dev-organization/), even if the subscription is for one user. The subscription is identical for everyone in the organization and one license is required for every member (unless their [role](/gk-dev/gk-dev-organization/#roles) does not use a license).
+Last updated: July 2025
+
+Subscriptions in GitKraken Dev are tied directly to an [organization](/gk-dev/gk-dev-organization/), even if there is only one user.
+
+All members of an organization share the same subscription, and each active member requires a license. Some [roles](/gk-dev/gk-dev-organization/#roles) do not consume a license.
***
## How to purchase
-To purchase a subscription for the first time follow these steps:
-1. Visit [gitkraken.dev](https://gitkraken.dev).
-2. Login with your [GitKraken account](/gk-dev/gk-dev-account/) or create an account.
-3. Select your organization in the left panel and select "Purchase Subscription" (remember you need to have a [role](/gk-dev/gk-dev-organization/#roles) with permission to purchase).
-4. Set the desired number of user seats. Then, select the tier that is best for your organization (Pro, Teams, or Enterprise). There are links at the bottom of each while can further elaborate on the differences.
-5. Fill out the Organization name, First name, Last name, and country or region. If you have a promo code, select "Have a promo code?" and provide it. Proceed by selecting "Payment details".
-6. Select the desired payment method and proceed with filling out the required billing information if needed. Then select "Review your order".
-7. Select the "Buy now" button to complete your transaction.
-8. If you added more licenses than there are members in the organization to claim, you will be taken to the "Add Users" screen.
-
-If you encounter trouble while purchasing and you have verified your payment method, please don’t hesitate to contact us for support.
+To purchase a subscription for the first time: + +1. Visit [gitkraken.dev](https://gitkraken.dev?source=help_center&product=gitkraken_dot_dev). +2. Log in with your [GitKraken account](/gk-dev/gk-dev-account/) or create one. +3. Select your organization in the left panel, then click **Purchase Subscription**. You’ll need a [role](/gk-dev/gk-dev-organization/#roles) with billing permissions. +4. Set the number of user seats. Choose the subscription tier that best fits your organization (Pro, Teams, or Enterprise). Each tier includes a link to learn more. +5. Enter your organization name, first and last name, and your country or region. If you have a promo code, click **Have a promo code?** to enter it. Click **Payment details** to continue. +6. Select a payment method and complete the billing information. Then click **Review your order**. +7. Click the **Buy now** button to complete your purchase. +8. If you added more licenses than there are users to assign them to, you’ll be redirected to the **Add Users** screen. + +If you encounter issues while purchasing and have verified your payment method, please contact us for support.
+ 
+ Only the owner, admins, and billing contacts have permission to cancel.
+Only the Owner, Admins, and Billing Contacts can cancel subscriptions.
+
+ 
+
+- [Assign licenses to users](/gk-dev/gk-dev-organization/#add-users)
+- [Set up Single Sign-On (SSO)](/gk-dev/gk-dev-single-sign-on/)
+- [Explore GitKraken.dev Home](/gk-dev/gk-dev-home/)
\ No newline at end of file
diff --git a/gk-dev/gk-dev-trials.md b/gk-dev/gk-dev-trials.md
index 9e673a7..1bdcfe0 100644
--- a/gk-dev/gk-dev-trials.md
+++ b/gk-dev/gk-dev-trials.md
@@ -1,4 +1,4 @@
----
+---
title: GitKraken Trials
description: Learn about GitKraken Trials
@@ -6,24 +6,49 @@ taxonomy:
category: gk-dev
---
-
-## Trials
+Last updated: June 2025
-Both GitKraken Desktop and GitLens offer 14-day trials of Pro. You can initiate these trials by logging into the corresponding app with a GitKraken account for the first time. Each trial is separate, so starting a 14-day trial with your GitKraken account in one app does not start it for the other.
-
-***
-
-### Business Plan Trials
+## Trial options
-Business plan trials are available for groups of users that would like to try the [GitKraken DevEx platform](https://www.gitkraken.com/devex) across members of their team, company, or organization. After a Business plan trial is started, it will be active for 30 days. The duration of the Business plan trial is shared by everyone in the organization.
-
-To start a Business plan trial:
-
-1. Visit [gitkraken.dev](https://gitkraken.dev/)
-2. Login with your GitKraken account
-5. Navigate to [Users](https://gitkraken.dev/users) and add a user(s)
-6. Once users are added, your extended organization trial has begun
-
-It is not possible for a user to be a member of more than one Business plan trial at a time. Once the Business plan trial has lapsed, an owner cannot start another multi-user trial.
-Each user can only join one Business trial. Owners can’t start another Business trial after the first one ends.
+