How to Configure Teams in AllSpice
Teams allow you to control role-based permissions inside your AllSpice organization. You can define who can read or write files, push or pull from repositories, create design reviews, manage releases, and more.
Team configuration also determines which users count as billable committers.
If you only need to adjust paid committer teams, see:
How to switch teams between committer and collaborator
Recommended Team Structure
Most organizations benefit from at least two teams:
Designers
- Full read and write access to repositories
- Can push changes and modify files
- Count as billable committers (if File permission is set to Write)
Reviewers
- Read access to files
- Write access to Issues and Design Reviews
- Do not modify source files
- Do not count as billable committers
This structure:
- Protects production designs
- Keeps billing intentional
- Separates authorship from review
How to View Your Teams
-
Navigate to your Organization main page
/v1/docs/how-to-view-your-organization -
Click the Teams tab.
Create a new Team for Designers
Below is an interactive walkthrough demonstrating how to create a new Team and configure repository permissions for your Designers who need write access to add and update files.
Step-by-step instructions to create a Designer team
-
Click “+ New Team”
.png)
-
Enter a team name (e.g., Designers)
.png)
-
Choose repository access scope
Select All repositories if this team should access every repo automatically.
.png)
- Set permission level
Select General access to configure permissions by section.
- Configure section permissions
For a Designer team, enable Write access for:
- Files
- Issues
- Design Reviews
- Releases
- Wiki
- Projects
Write permission enables git operations and web file changes.
Step-by-step permissions
.png)
.png)
.png)
.png)
.png)
.png)
.png)
- External integrations (optional)
Disable unless required:
- External wiki
- External issue tracker
.png)
.png)
-
Click “Create Team”
.png)
-
Add team members
Search for users or enter email addresses to assign members.
.png)
Your Designer team is now configured.
.png)
Create new Team for Reviewers
Below is an interactive walkthrough demonstrating how to create a new Team and configure repository permissions for Reviewers
Step-by-step guide to create a new team for Reviewers
-
Click the "+ New Team" button to begin creating a new team in your organization.
.png)
-
Enter a descriptive team name to help identify the group’s role or purpose.
.png)
-
Select "Specific repositories" to limit this team's access to only chosen repositories, enhancing access control.
.png)
-
Enable external wiki access if your team needs to reference documentation outside the platform.
.png)
-
Allow access to external issues for integrating with an outside issue tracker system.
.png)
-
Finalize team creation by clicking "Create Team" after configuring all access and permissions.
.png)
-
Switch to the "repositories" tab to review or assign repositories to this team.
.png)
-
Search for an existing repository to manage or add additional access for your team.
.png)
-
Select the desired repository from the dropdown to prepare it for team access.
.png)
-
Add the selected repository to the team's list to grant access.
.png)
-
Type in the repository name for further additions to the team's access list.
.png)
-
Choose another repository from the suggestions to add it to this team's access.
.png)
-
Assign the repository to the team by clicking the "Add" button to provide the appropriate access.
.png)
-
Congratulations! You've created a Team for Reviewers. They can view Design Reviews and make comments like requesting changes.
Understanding Team Settings
Whether creating a new team or editing an existing one, the configuration form is the same.
Team Name
Choose a name aligned with job function. Clear naming helps manage security and billing.
Examples:
- Committers
- Collaborators
- EngineeringReview
- EngineeringDesign
- Designers
- Contractors
- Technicians
- Purchasing
- Planning
- ContractManufacturers
Description
Use the description to clarify the purpose of the team and what level of access it should have.
Repository Access
Specific repositories (recommended for restricted access)
Only selected repositories are accessible. New repos are not automatically added.
All repositories
Team members automatically gain access to new repositories. Not recommended for external users.
Create repositories
Allows team members to create new repositories.
This does not affect billable committer count.
Permission Level
Administrator Access
- Full admin access to repositories
- All members count as billable committers
General Access
Permissions are controlled by section below.
Section Permissions
Files
- Read: View all files
- Write: Push/pull, modify files, commit changes
⚠️ Billing Note:
Only File Write permission affects billable committer count.
Issues
- Read: View issues and milestones
- Write: Create, edit, comment, attach files
Design Reviews
- Read: View pull requests and changed files
- Write: Create, update, comment, attach files
Releases
- Read: View releases
- Write: Create releases and attach files
Wiki
- Read: View wiki
- Write: Edit and create wiki pages
Projects
- Read: View Organization Project boards
- Write: Create and manage Organization Project boards
Packages
Currently disabled.
External Integrations
- Enable external wiki if using an outside documentation system
- Enable external issues if linking to an external issue tracker
Frequently Asked Questions
Does Write access always make someone billable?
No. Only Write access to Files or Administrator Access counts toward billable committer status.
Should external contractors have All repositories enabled?
No. Use Specific repositories to limit exposure.
What’s the difference between Administrator and General access?
Administrator grants full control across repositories and is a billable Team.
General access allows section-level permission control, including read+comment access. Most teams should use General access.
Can I edit a team after creating it?
Yes. Editing a team uses the same configuration form.