ArchDoc Documentation

Team Management Overview

Managing your team in ArchDoc

Team Management Overview

Learn how to manage your team members, roles, and permissions in ArchDoc.

Team Structure

Each ArchDoc organization (company) has:

  • Team Members: Users who belong to the organization
  • Roles: Admin or Member
  • Invitations: Pending invites to join

Roles and Permissions

Admin Role

Admins have full control:

PermissionAdmin
Create documents
Edit any document
Delete any document
Invite team members
Remove team members
Change user roles
Connect GitHub
Manage billing

Member Role

Members can contribute but have limited admin access:

PermissionMember
Create documents
Edit documents
Delete own documents
Participate in sign-offs
Comment on documents
Invite team members
Manage team
Manage billing

Accessing Team Settings

  1. Navigate to Dashboard
  2. Click Settings in the sidebar
  3. You'll see the Team Members section with current members and the Invite Member button

Only Admins can see and manage the full team settings (invite/remove members, change roles, update organization name). Members can participate in sign-offs and comments but cannot change team configuration.

Team Management Features

Seat Limits

Your subscription determines how many team members you can have:

PlanSeats IncludedAdditional Seats
Free2N/A
Base5$9/seat/month
Premium50Included

Checking Seat Usage

  1. Go to Dashboard > Billing
  2. See "Seats Used: X / Y"
  3. Shows current team size vs. limit

Adding More Seats (Base Plan)

  1. Go to Dashboard > Billing
  2. Click Add Seats
  3. Enter number of additional seats
  4. Complete payment

Pending Invitations

Track invitations that haven't been accepted:

  1. Go to Dashboard > Settings
  2. Scroll to Pending Invitations
  3. See email, role, and status

You can:

  • Resend an invitation
  • Cancel a pending invitation

Best Practices

Choose Roles Wisely

  • Most team members should be Members
  • Only key people need Admin access
  • Admins can manage billing—consider carefully

Plan for Team Size

  • Know your seat limits
  • Invite only active participants
  • Remove inactive members to free seats

Onboard New Members

  • Send them documentation links
  • Introduce them to existing documents
  • Assign them to relevant sign-offs

Security Considerations

Access Control

  • Users only see their organization's data
  • Role-based permissions enforced
  • Audit trail for activities

Removing Access

  • When someone leaves, remove them promptly
  • Their documents remain (ownership transfers)
  • Sign-offs they provided stay on record

Password Policies

  • Minimum 8 characters required
  • Encourage strong passwords
  • Consider enabling 2FA when available

On this page