Finding Your Bitbucket Server Support Entitlement Number (SEN)
Support policies
On this page
Related content
- Enabling SSH access to Git repositories in Bitbucket Server
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Securing Bitbucket Server with Apache using SSL
- Bitbucket Server webhook is not providing git URL is response payload.
- Proxying and securing Bitbucket Server
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- Securing Bitbucket Server behind nginx using SSL
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
- Bitbucket Server HTTPS request is redirecting back to HTTP URL during application links creation
Your Support Entitlement Number (SEN) is required when raising a support request in our Support system: http://support.atlassian.com.
See How to find your Support Entitlement Number (SEN) in the Support space for more general information about how Atlassian Support uses this number.
The three ways of finding your SEN are described below.
Method 1 — Check the Bitbucket Server Administration Interface
To find your SEN in the Bitbucket Server administration interface:
- Click the
icon in the Bitbucket Server header. - Click Licensing in the left navigation panel (under 'Settings'). The SEN is shown as in the screenshot below:
Method 2 — Check my.atlassian.com
To find your SEN via my.atlassian.com:
- Log into my.atlassian.com as the Account Holder or Technical Contact for your Bitbucket Server product.
- The SEN will be shown, as per the screenshot below:
Method 3 — Check your Atlassian Invoice
Your Support Entitlement Number (SEN) appears on the third page of your Atlassian Invoice.
Last modified on Nov 17, 2020
Related content
- Enabling SSH access to Git repositories in Bitbucket Server
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Securing Bitbucket Server with Apache using SSL
- Bitbucket Server webhook is not providing git URL is response payload.
- Proxying and securing Bitbucket Server
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- Securing Bitbucket Server behind nginx using SSL
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
- Bitbucket Server HTTPS request is redirecting back to HTTP URL during application links creation
Powered by Confluence and Scroll Viewport.