bit.dev Account · Bit

User settings

To view the profile page, log-in and click on your avatar at the top right page corner. Then click on the profile name. Select the settings page where you can:

Change the avatar
Update password
Add and update email addresses
Delete organizations

You must be an admin to delete an organization.
Leave organizations

You can leave an organization on which you are an admin only if there are other admins on that organization.
Manage SSH keys for accessing the account
Delete your account

Deleting your account is possible only if you are not an admin on any organization.

Organization settings

To view an organization, select the organization from the avatar's drop-down list. An organization's admin can:

Click on the edit button to change the organization's image, name, homepage, or description.
Click on the Settings button to edit the organization's members, billing and integrations.

Organization Billing

Click here to see bit.dev plans.

Charging

Charging occurs at the monthly anniversary of the subscription (e.g., on the 17th of every month).

Adding and Removing Members

Members added to the organization are granted access immediately to the organization's features, according to the plan.
Members removed from the organization revoke their access and support immediately when deleted.
Charging is according to the number of the actual number of members on the day of subscription's charge.

Canceling a Paid Subscription

Canceling a subscription takes effect at the end of the billing period. Canceling a plan does not delete the private collections. However, they are no longer accessible.
Reactivating a subscription will renew the monthly subscription fee. If the account had private collections, you would regain access to them immediately.

Charging Issues

If there is an issue charging your payment method, the account will retain a 60 days grace period, in which all account members will still have access to premium features and private code components. If we could not resolve the issue by the end of the grace period, access to premium features and private collections is removed from the organization account.

Collections management

Change the settings of the collections by clicking the settings on the collection page. You can access the collection page via the url: bit.dev/<owner>/<collection>. Then click the settings button. To make modifications to the collection you need to have admin privileges.

Collection's settings

On the collection page you can edit the collection's description or access the settings page to:

Change the collection's license.
Change the collection's visibility (public / private).
Delete the collection from bit.dev.
Manage the users that can access the collection and change their permissions.

Users and Roles

Use the permission tab of the collection to add, remove, and change permissions for users for the collection.
Collection's members are assigned with 3 possible roles:

Role	Admin	Developer	Viewer
View Components*	Yes	Yes	Yes
Import Components*	Yes	Yes	Yes
Install Components *	Yes	Yes	Yes
Export Components	Yes	Yes	No
Manage members	Yes	No	No
Edit collection's information	Yes	No	No
Define integrations	Yes	No	No

*Viewing, importing and installing is available for all users for public collections.

Transfer collections

Here are the steps to transfer collections that were created on personal account to an organizations account (or between different owners or collections).

Make sure you have both collections defined on bit.dev and that you have writing permissions to the new collection, and at least viewing permissions to the old collection.

# Create and empty directory and initialize it with a bit scope
$ mkdir <collection-dir> # create an empty directory
$ cd <collection-dir>
$ bit init
successfully initialized a bit workspace.

# Import all components from the old collection to the local scope
$ bit import "<old-owner>.<old-collection-name>/*"
successfully imported x components

# Export all components to the new scope rewiring all their dependencies to the new collection
$bit export <new-owner>.<new-collection> --set-current-scope --rewire --include-dependencies --all
# bit requests for approval
exported 4 components to scope <new-owner>.<new-collection>