Skip to main content

Team Management

Collaborate with your team by inviting members, assigning roles, and managing permissions.

Team Context

Teams are your organization-level container. Team management features are available regardless of workspace selection. For workspace-specific resources like templates and API keys, see Teams & Workspaces.

Overview​

Rynko uses a two-level hierarchy: Teams and Workspaces. A Team is your organization, controlling billing and member access. Within a team, you create Workspaces to organize different projects.

This page covers team-level management. For the full picture, see Teams & Workspaces.

Team Roles​

Owner​

  • Full access to all features
  • Can delete team
  • Can manage billing
  • Cannot be removed

Admin​

  • Manage team members
  • Create/edit/delete templates
  • Generate documents
  • View analytics
  • Manage API keys

Member​

  • Create/edit templates
  • Generate documents
  • View own analytics
  • Cannot manage team

Viewer​

  • View templates (read-only)
  • View document logs
  • View analytics
  • Cannot create or generate

Team vs. Workspace Permissions​

Team roles determine what a member can do across the organization:

ActionOwnerAdminMemberViewer
Manage billing✅❌❌❌
Invite members✅✅❌❌
Create workspaces✅✅❌❌
View team analytics✅✅❌❌
Access workspaces✅✅✅✅
Create templates✅✅✅❌
Generate documents✅✅✅❌

All team members can access all workspaces within the team (based on their role's permissions).

Inviting Members​

  1. Go to Settings → Team
  2. Click Invite Member
  3. Enter email address
  4. Select role
  5. Click Send Invitation

Member receives email invitation with signup link.

Managing Members​

Change Role​

  1. Find member in list
  2. Click role dropdown
  3. Select new role
  4. Changes apply immediately

Remove Member​

  1. Click "..." menu on member row
  2. Select Remove
  3. Confirm removal
  4. Member loses access immediately

Resend Invitation​

For pending invitations, click Resend to send email again.

Team Activity​

View recent team activity:

  • Member joined/left
  • Templates created/modified
  • Documents generated
  • API keys generated

Best Practices​

  • Use appropriate roles: Grant least privilege needed
  • Review regularly: Audit team members quarterly
  • Remove promptly: Remove members when they leave
  • Document access: Keep records of who has access

Related: Settings | API Keys