There are identity forms available on Now, called "scopes": Users and teams.

When you signed up for our service the first time, you have created a user account. With this type of identity, you can enjoy all the features Now has to offer and access to the data created by those features is limited to just your user account.

Sharing Your Data with Other People

Firstly, it is important to understand that you should never give any other person access to your own user account, not under any circumstance.

If you would like to share access to your deployments, domains, secrets or other resources with a co-worker, family member or any other kind of person, they first need to create their own user account on Now.

Point them to this URL for signing up:

Once they have created their own user account, you can create a team by clicking on the scope selector on the top left, and then choosing "Create a Team":

Creating a team from the account picker from the account dashboard.

After clicking the link, you will be asked to select whether you would like to set up your team with GitHub directly (which we highly suggest) and then to enter the URL of your future team. For this, please choose an accurate representation of your team's name:

Setting the team URL when creating a team.

After you filled out the URL, you only need to hit "SAVE" in order for your team to be created.

Next up, please click on the "Members" section of the menu on the top right. You will be presented with the list of people that are part of your team. At the moment, the list should only contain your own user account, as you have not yet invited any other people.

In order to invite another person, click the "INVITE" button on the right and enter the email address of the user account of the person you would like to invite:

Inviting additional team members from the team members dashboard.

After clicking the "INVITE" button the person is now part of your team and has access to all the resources (deployments, domains, certificates, etc.) created within your team.

Switching Between Users and Teams

If you are part of one or multiple teams, you might want to change whether you are deploying to one of those teams or to your own user account.

To do this, you have several options depending on the client you are using:


Click on your avatar on the top left, then select the team of your choice:

Switching teams from the account picker in the dashboard.

Now Desktop

Click on the triangle in your menubar, then select the avatar of your team in the bar in the bottom of the Now Desktop window:

Switching teams from the Now Desktop account bar.


Run the following command and pick the user or team of your choice:

now switch

You can also run this command with the slug of a team or username you would like to switch to:

now switch <team-slug|username>

Changing the User or Team Settings

Just like different scopes have different resources contained within them (access is limited to people that are members of the scope), they also allow for different configurations.

As you read above, all our interfaces allow switching between scopes without hassle. Once you have switched to the scope of your choice on the dashboard, you can click the little cog icon on the top left in order to configure the scope:

Switching teams from the Now Desktop account bar.

After clicking the button, you will be presented a series of fields that you can adjust to your needs. Any changes you make to those fields are entirely unrelated to any other scopes and do not affect them in any way.

Only the scope that is indicated using the avatar icon on the top left is affected.

Selecting a Scope for API Requests

When communicating with our API, all interactions only consider the resources contained within your own user account by default.

If you want to access a team's resources, you first need to find out the ID of the team.

This can be accomplished by switching to the team in Now CLI (as described above) and then opening the file located under ./.now/config.json, which will reveal a property named currentTeam within it. This property contains the ID of your team.

Now you can attach the ID to the URL of your requests like this:<team-id-here>

With this GET parameter attached, the response will of the URL above will now include only the deployments of the team matching the specified teamId.

However, you still need to attach a token of your user account as described here. In turn, this user account needs to be a member of the team you would like to access over the API.

Note: For more information on the teams API endpoint, see our API reference documentation.