Create Your First User
Your own login administers the account. Your own builds do not need a repository user: they publish and retrieve artifacts with a repository token you create while signed in. Your team needs repository users: accounts you invite from the admin portal, each with an email address of its own and a password they set and sign in to the portal with. Do not give one your own address. A user’s builds do not use that password: the user signs in, creates a repository token, and the build sends the token, with the user’s email address as the username wherever the client asks for one. Every guide on a repository’s Connect page sets a build up that way.
This guide walks through inviting one and setting what they can do.
How Access Works
Section titled “How Access Works”Two things control what a repository user can do, and both are set on that person’s page after the account exists:
- Repository access is account wide. A user either has read and write access to every repository in your account, or read only access to every repository. There is no per repository assignment.
- Administrator permissions are granted one area at a time: billing, repositories, software distribution, users and webhooks. A user you create has none of them.
The owner can also make someone an Admin, who manages all of those areas. See The Admin Role.
Inviting a User
Section titled “Inviting a User”Step 1: Open the Users Page
Section titled “Step 1: Open the Users Page”- Log in to the CloudRepo Administrator Portal
- Click Users in the sidebar
- Click Invite user
The form opens as the first row of the users table. Until you have invited anyone, the page reads “Only you so far.” and the form is already open.
Step 2: Fill In the Row
Section titled “Step 2: Fill In the Row”The row asks for two things:
- Email address: where the invitation goes. It becomes their username for repository access
- Repository access: Read (download from every repository) or Read + Write (download from and publish to every repository). Read is chosen for you
Send invitation stays disabled until the address is valid. An address that already has an invitation waiting, or that is already a member, is pointed out before you send.

Step 3: Send the Invitation
Section titled “Step 3: Send the Invitation”Click Send invitation. If you have not confirmed your identity in the last 15 minutes, a Confirm Your Identity dialog comes first: enter your password and click Confirm. A confirmation you obtained with your password stops working once you enroll a second factor; confirm again with that factor.

The row becomes the person waiting to join, marked Invited, and says when the invitation expires. We email them a link to set their own password. The link expires in 7 days. In an organization that requires single sign-on, the invitation asks them to sign in with your company’s single sign-on. Until they join, Resend sends a new link, and Revoke stops the link working.

They set their own password, so nobody else has it. CloudRepo never asks you to choose or send one. In an organization that requires single sign-on, the invitation asks them to sign in with your company’s single sign-on.
Changing What a User Can Do
Section titled “Changing What a User Can Do”Click a row in the Users list to open that person’s page. Its title is their name, or their address when there is no name.
Read Only Access
Section titled “Read Only Access”A new account gets the repository access you chose when you invited them: with Read, Read only user is on for it; with Read + Write, it is off, which the switch states as “User has read and write access to all repositories”. To limit that user to reading, open the person, select Change access, then turn on Read only user.
Administrator Permissions
Section titled “Administrator Permissions”These toggles delegate account administration, one area each:
- Manage billing
- Manage repositories
- Manage software distribution
- Manage users
- Manage webhooks
They are independent of repository access, and they are all off for a user you invite. See User Management for what each one covers.
An Admin has every one of these. Only the owner makes someone an Admin: see The Admin Role.
Resetting a Password
Section titled “Resetting a Password”Click Reset password under Sign-in on the person’s page, then Reset password. Their current password stops working at once, in the portal and in builds, and CloudRepo emails them a link to choose a new one. See Reset a User’s Password.
Removing a User
Section titled “Removing a User”- Open the person’s page from the Users list
- Click Delete User
- Type the user’s email address into the confirmation box. The dialog warns that “This action cannot be undone. The user will be permanently removed”, and its Delete User button stays disabled until the address matches
- Click Delete User
Best Practices
Section titled “Best Practices”-
Grant the minimum. An invitation starts on Read. Choose Read + Write only for someone who publishes.
-
One account per person, and an organization token per pipeline. Give a CI pipeline an organization token, which the owner or an Admin creates and which belongs to your organization rather than to a person, instead of a teammate’s token, so that removing a teammate does not interrupt the build.
-
Review the list periodically. The Users page shows every account and its access level in a single table.
Troubleshooting
Section titled “Troubleshooting”- A user can download but cannot upload: check whether Read only user is turned on for that account. Open their page, select Change access and turn it off to restore write access.
Next Steps
Section titled “Next Steps”- Repository Tokens: Create One and Authenticate: Sign in as the new user and create the repository token its builds send, with the user’s email address as the username
- Basic Configuration Examples: Configure your development tools
- User Management: Full reference for user settings and permissions
- Continuous Integration and Deployment: Set up CI/CD integration