realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/subscriptions/gitlab_com/index.md
Pirate Praveen d8d5ad1a24 New upstream version 13.12.3+ds1
2021-06-08 01:23:25 +05:30

19 KiB
Raw Blame History

stage group info type
Fulfillment Purchase To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments index, reference

GitLab SaaS subscription (PREMIUM SAAS)

GitLab SaaS is the GitLab software-as-a-service offering. You don't need to install anything to use GitLab SaaS, you only need to sign up and start using GitLab straight away.

This page reviews the details of your GitLab SaaS subscription.

Choose a GitLab SaaS tier

Pricing is tier-based, so you can choose the features that fit your budget. For information on the features available for each tier, see the GitLab SaaS feature comparison.

Choose the number of users

NOTE: Applied only to groups.

A GitLab SaaS subscription uses a concurrent (seat) model. You pay for a subscription according to the maximum number of users enabled at once. You can add and remove users during the subscription period, as long as the total users at any given time doesn't exceed the subscription count.

Every occupied seat is counted in the subscription, with the following exception:

  • Members with Guest permissions on an Ultimate subscription.

NOTE: To support the open source community and encourage the development of open source projects, GitLab grants access to Ultimate features for all GitLab SaaS public projects, regardless of the subscription. GitLab also provides qualifying open source projects with 50,000 CI minutes and free access to the Ultimate tier for groups through the GitLab for Open Source program.

Obtain a GitLab SaaS subscription

To subscribe to GitLab SaaS:

  1. Create a user account for yourself using our sign up page.
  2. Create a group. GitLab groups help assemble related projects together allowing you to grant members access to several projects at once. A group is not required if you plan on having projects inside a personal namespace.
  3. Create additional users and add them to the group.
  4. Select the GitLab SaaS plan through the Customers Portal.
  5. Link your GitLab SaaS account with your Customers Portal account. Once a plan has been selected, if your account is not already linked, GitLab prompts you to link your account with a Sign in to GitLab.com button.
  6. Select the namespace from the drop-down list to associate the subscription.
  7. Proceed to checkout.

NOTE: You can also go to the My Account page to add or change the GitLab SaaS account link.

View your GitLab SaaS subscription

To see the status of your GitLab SaaS subscription, log in to GitLab SaaS and go to the Billing section:

NOTE: You must have Owner level permissions to view the billing page.

The following table describes details of your subscription:

Field Description
Seats in subscription If this is a paid plan, represents the number of seats you've bought for this group.
Seats currently in use Number of seats in use. Select See usage to see a list of the users using these seats. For more details, see Seat usage.
Max seats used Highest number of seats you've used.
Seats owed Seats owed = Max seats used - Seats in subscription.
Subscription start date Date your subscription started. If this is for a Free plan, it's the date you transitioned off your group's paid plan.
Subscription end date Date your current subscription ends. Does not apply to Free plans.

Seat usage

To view a list of seats being used, go to Settings > Billing. Under Seats currently in use, select See usage.

The Seat usage page lists all users occupying seats. Details for each user include:

  • Full name
  • Username
  • Public email address (if they have provided one in their user settings)

The Seat usage listing is updated live, but the usage statistics on the billing page are updated only once per day. For this reason there can be a minor difference between the seat usage listing and the billing page.

Search seat usage

Introduced in GitLab 13.8.

To search users in the Seat usage page, enter a string in the search field. A minimum of 3 characters are required.

The search returns those users whose first name, last name, or username contain the search string.

For example:

First name Search string Match ?
Amir ami Yes
Amir amr No

Subscription expiry

When your subscription expires, you can continue to use paid features of GitLab for 14 days. On the 15th day, paid features are no longer available. You can continue to use free features.

To resume paid feature functionality, purchase a new subscription.

Renew your GitLab SaaS subscription

To renew your subscription:

  1. Prepare for renewal by reviewing your account.
  2. Renew your GitLab SaaS subscription.

Prepare for renewal by reviewing your account

The Customers Portal is your tool for renewing and modifying your subscription. Before going ahead with renewal, log in and verify or update:

  • The invoice contact details on the Account details page.
  • The credit card on file on the Payment Methods page.

NOTE: Contact our support team if you need assistance accessing the Customers Portal or if you need to change the contact person who manages your subscription.

It's important to regularly review your user accounts, because:

  • A GitLab subscription is based on the number of users. You could pay more than you should if you renew for too many users, while the renewal fails if you attempt to renew a subscription for too few users.
  • Stale user accounts can be a security risk. A regular review helps reduce this risk.

Seats owed

A GitLab subscription is valid for a specific number of users. For details, see Choose the number of users.

If the number of billable users exceeds the number included in the subscription, known as the number of seats owed, you must pay for the excess number of users before renewal.

Seats owed example

You purchase a subscription for 10 users.

Event Billable members Maximum users
Ten users occupy all 10 seats. 10 10
Two new users join. 12 12
Three users leave and their accounts are removed. 9 12

Seats owed = 12 - 10 (Maximum users - users in subscription)

Renew or change a GitLab SaaS subscription

Starting 30 days before a subscription expires, GitLab notifies group owners of the date of expiry with a banner in the GitLab user interface.

We recommend following these steps during renewal:

  1. Prune any inactive or unwanted users.
  2. Determine if you have a need for user growth in the upcoming subscription.
  3. Log in to the Customers Portal and beneath your existing subscription, select the Renew button.
  4. Review your renewal details and complete the payment process.
  5. Select Confirm purchase.

Your updated subscription is applied to your namespace on the renewal period start date.

An invoice is generated for the renewal and available for viewing or download on the View invoices page. If you have difficulty during the renewal process, contact our support team for assistance.

For details on upgrading your subscription tier, see Upgrade your GitLab SaaS subscription tier.

Automatic renewal

To view or change automatic subscription renewal (at the same tier as the previous period), log in to the Customers Portal, and:

  • If you see a Resume subscription button, your subscription was canceled previously. Click it to resume automatic renewal.
  • If you see Cancel subscription, your subscription is set to automatically renew at the end of the subscription period. Click it to cancel automatic renewal.

With automatic renewal enabled, the subscription automatically renews on the expiration date without a gap in available service. An invoice is generated for the renewal and available for viewing or download in the View invoices page. If you have difficulty during the renewal process, contact our support team for assistance.

Add users to your subscription

You can add users to your subscription at any time during the subscription period. The cost of additional users added during the subscription period is prorated from the date of purchase through the end of the subscription period.

To add users to a subscription:

  1. Log in to the Customers Portal.
  2. Navigate to the Manage Purchases page.
  3. Select Add more seats on the relevant subscription card.
  4. Enter the number of additional users.
  5. Select Proceed to checkout.
  6. Review the Subscription Upgrade Detail. The system lists the total price for all users on the system and a credit for what you've already paid. You are only be charged for the net change.
  7. Select Confirm Upgrade.

The following is emailed to you:

  • A payment receipt. You can also access this information in the Customers Portal under View invoices.

Upgrade your GitLab SaaS subscription tier

To upgrade your GitLab tier:

  1. Log in to the Customers Portal.
  2. Select Upgrade on the relevant subscription card on the Manage purchases page.
  3. Select the desired upgrade.
  4. Confirm the active form of payment, or add a new form of payment.
  5. Check the I accept the Privacy Policy and Terms of Service checkbox.
  6. Select Confirm purchase.

When the purchase has been processed, you receive confirmation of your new subscription tier.

See your subscription and billable users in GitLab.com

To view information about your subscription and occupied seats:

  1. Go to your group's Settings > Billing page.
  2. In the Seats currently in use area, select See usage.

Remove billable user

To remove a billable user:

  1. Go to your group's Settings > Billing page.
  2. In the Seats currently in use area, select See usage.
  3. In the row for the user you want to remove, on the right side, select the ellipsis and Remove user.
  4. Re-type the username and select Remove user.

If you add a member to a group by using the share a group with another group feature, you can't remove the member by using this method. Instead, you can either:

  • Remove the member from the shared group. You must be a group owner to do this.
  • From the group's membership page, remove access from the entire shared group.

CI pipeline minutes

CI pipeline minutes are the execution time for your pipelines on GitLab shared runners. Each GitLab SaaS tier includes a monthly quota of CI pipeline minutes:

  • Free: 400 minutes
  • Premium: 10,000 minutes
  • Ultimate: 50,000 minutes

Quotas apply to:

  • Groups, where the minutes are shared across all members of the group, its subgroups, and nested projects. To view the group's usage, navigate to the group, then Settings > Usage Quotas.

  • Your personal account, where the minutes are available for your personal projects. To view and buy personal minutes:

    1. In the top-right corner, select your avatar.
    2. Select Edit profile.
    3. In the left sidebar, select Usage Quotas.

Only pipeline minutes for GitLab shared runners are restricted. If you have a specific runner set up for your projects, there is no limit to your build time on GitLab SaaS.

The available quota is reset on the first of each calendar month at midnight UTC.

When the CI minutes are depleted, an email is sent automatically to notify the owner(s) of the namespace. You can purchase additional CI minutes, or upgrade your account to a higher plan. Your own runners can still be used even if you reach your limits.

Purchase additional CI minutes

If you're using GitLab SaaS, you can purchase additional CI minutes so your pipelines aren't blocked after you have used all your CI minutes from your main quota. You can find pricing for additional CI/CD minutes in the GitLab Customers Portal. Additional minutes:

  • Are only used after the shared quota included in your subscription runs out.
  • Roll over month to month.

To purchase additional minutes for your group on GitLab SaaS:

  1. From your group, go to Settings > Usage Quotas.

  2. Select Buy additional minutes and GitLab directs you to the Customers Portal.

  3. Locate the subscription card that's linked to your group on GitLab SaaS, click Buy more CI minutes, and complete the details about the transaction.

  4. Once we have processed your payment, the extra CI minutes are synced to your group namespace.

  5. To confirm the available CI minutes, go to your group, then Settings > Usage Quotas.

    The Additional minutes displayed now includes the purchased additional CI minutes, plus any minutes rolled over from last month.

To purchase additional minutes for your personal namespace:

  1. In the top-right corner, select your avatar.

  2. Select Edit profile.

  3. In the left sidebar, select Usage Quotas.

  4. Select Buy additional minutes and GitLab redirects you to the Customers Portal.

  5. Locate the subscription card that's linked to your personal namespace on GitLab SaaS, click Buy more CI minutes, and complete the details about the transaction. Once we have processed your payment, the extra CI minutes are synced to your personal namespace.

  6. To confirm the available CI minutes for your personal projects, go to the Usage Quotas settings again.

    The Additional minutes displayed now includes the purchased additional CI minutes, plus any minutes rolled over from last month.

Be aware that:

  • If you have purchased extra CI minutes before the purchase of a paid plan, we calculate a pro-rated charge for your paid plan. That means you may be charged for less than one year because your subscription was previously created with the extra CI minutes.
  • After the extra CI minutes have been assigned to a Group, they can't be transferred to a different Group.
  • If you have used more minutes than your default quota, these minutes will be deducted from your Additional Minutes quota immediately after your purchase of additional minutes.

Storage subscription

Projects have a free storage quota of 10 GB. To exceed this quota you must first purchase one or more storage subscription units. Each unit provides 10 GB of additional storage per namespace. A storage subscription is renewed annually. For more details, see Usage Quotas.

When the amount of purchased storage reaches zero, all projects over the free storage quota are locked. Projects can only be unlocked by purchasing more storage subscription units.

Purchase more storage

To purchase more storage for either a personal or group namespace:

  1. Sign in to GitLab SaaS.
  2. From either your personal homepage or the group's page, go to Settings > Usage Quotas.
  3. For each locked project, total by how much its Usage exceeds the free quota and purchased storage. You must purchase the storage increment that exceeds this total.
  4. Click Purchase more storage and you are taken to the Customers Portal.
  5. Click Add new subscription.
  6. Scroll to Purchase add-on subscriptions and select Buy storage subscription.
  7. In the Subscription details section select the name of the user or group from the dropdown.
  8. Enter the desired quantity of storage packs.
  9. In the Billing information section select the payment method from the dropdown.
  10. Select the Privacy Policy and Terms of Service checkbox.
  11. Select Buy subscription.
  12. Sign out of the Customers Portal.
  13. Switch back to the GitLab SaaS tab and refresh the page.

The Purchased storage available total is incremented by the amount purchased. All locked projects are unlocked and their excess usage is deducted from the additional storage.

Customers Portal

The GitLab Customers Portal enables you to manage your subscriptions and account details.

Contact Support

Learn more about:

We also encourage all users to search our project trackers for known issues and existing feature requests in the GitLab project.

These issues are the best avenue for getting updates on specific product plans and for communicating directly with the relevant GitLab team members.

Troubleshooting

Credit card declined

If your credit card is declined when purchasing a GitLab subscription, possible reasons include:

  • The credit card details provided are incorrect.
  • The credit card account has insufficient funds.
  • You are using a virtual credit card and it has insufficient funds, or has expired.
  • The transaction exceeds the credit limit.
  • The transaction exceeds the credit card's maximum transaction amount.

Check with your financial institution to confirm if any of these reasons apply. If they don't apply, contact GitLab Support.