Create Teams
Set up workspaces for your organization
Manage Members
Control access with role-based permissions
Switch Workspaces
Move between personal and team contexts
Share Resources
Collaborate on projects, agents, automations, and more
Creating Teams
Teams serve as collaborative workspaces where members can share projects, automations, agents, and other resources.1
Access Workspace Switcher
Click the workspace switcher in the sidebar to open the workspace menu
2
Create New Team
Select “Create Team” from the dropdown menu
3
Configure Team
Provide a team name and optional description for your new team
4
Automatic Ownership
You’ll automatically become the team owner with full administrative privileges
Team Roles & Permissions
Teams use role-based access control (RBAC) to manage what members can do:Owner
Owner
Full Control
- Manage all team members and invitations
- Delete the team
- Access and modify all team resources
Admin
Admin
Administrative Access
- Manage team members and send invitations
- Create, edit, and delete team resources
- Cannot delete the team
Member
Member
Standard Access
- Create and manage their own resources within the team
- View all team resources
- Cannot manage other team members
- Can leave the team voluntarily
Viewer
Viewer
Read-Only Access
- View team resources and activity
- Cannot create, edit, or delete resources
- Cannot manage team members
- Perfect for stakeholders and observers
Inviting Team Members
Team owners and admins can invite new members via email:1
Navigate to Team Settings
Go to your team settings page from the workspace switcher
2
Send Invitation
Click “Invite Members”, enter the email address, and select a role
3
Email Notification
The invitee will receive an email invitation with acceptance link
4
Accept or Decline
Invitees can accept or decline from their Palmier dashboard
Invitation Details
- Invitations expire after 7 days
- Only registered Palmier users can accept invitations
- Pending invitations can be cancelled by admins/owners
Workspace Switching
The workspace switcher in the sidebar allows you to seamlessly move between your personal workspace and team workspaces.Personal vs Team Workspaces
Your Individual Space
- Default workspace containing personal projects and resources
- Only you have access to these resources
- Ideal for individual work and experimentation
- No collaboration features
Resource Scoping
When you switch workspaces, all resources are automatically filtered based on your current context:| Resource Type | Personal Workspace | Team Workspace |
|---|---|---|
| Runs | Your individual agent runs | Team member runs |
| Projects | Personal projects only | Team projects visible to all members |
| Automations | Your private automations | Shared team automations |
| Agents | Personal custom agents | Team-scoped agents available to all |
| Environments | Individual dev environments | Shared team environments |
| MCP | MCP connection with personal credentials | Shared across team agents |
| Secrets | Only accessible by you | Shared across team resources |
Resources created in a team workspace are visible to all team members according to their role permissions. Always verify your current workspace before creating sensitive resources.
Team members without access to a repository cannot view runs (job details) for that repository, even if they are part of the team.
Best Practices
Team Organization
Start Small
Begin with a core team of trusted collaborators and gradually expand as workflows mature
Clear Roles
Assign admin roles to team leads, member roles to contributors, and viewer roles to stakeholders
Naming Conventions
Use descriptive team names and establish consistent resource naming patterns
Regular Reviews
Periodically review team membership and remove inactive members
Teams provide the foundation for collaborative AI-powered development. Start with a small team, establish clear workflows, and gradually expand your collaborative practices as your organization grows.