Skip to main content

​
Team Invitations

Figr becomes more powerful when your entire product team can contribute. Here’s how to invite colleagues and set up effective collaboration workflows.

​
Inviting Team Members

1

Access Team Settings

From your project dashboard:
  • Click “Team” in the sidebar
  • Select “Invite Members”
  • Or use the ”+ Invite” button in the top bar
Team invitation button location in Figr interface
2

Add Email Addresses

Invite methods:
  • Individual Invites
  • Bulk Import
  • Domain-Based
Enter email addresses one by one:
john@company.com
sarah@company.com
mike@company.com
Best for: Small teams, specific role assignments
3

Assign Roles

Choose appropriate permissions for each team member:

Viewer

Can:
  • View all designs
  • Leave comments
  • Export standard formats
Cannot:
  • Create or edit designs
  • Change project settings
  • Invite other users
Perfect for: Stakeholders, executives, external reviewers

Editor

Can:
  • Create and edit designs
  • Upload assets and context
  • Collaborate in real-time
  • Access AI design features
Cannot:
  • Change project settings
  • Manage team members
  • Delete projects
Perfect for: Designers, PMs, engineers

Admin

Can:
  • Full editor permissions
  • Manage team members
  • Configure project settings
  • Access billing and usage
Perfect for: Project leads, design managers
4

Customize Invitation

Personal message (optional):
Hi team! I've set up our product design workspace in Figr. 
This will help us create designs that match our existing 
product and maintain consistency across features.

Looking forward to collaborating!
Include:
  • Context about why you’re using Figr
  • What they should focus on initially
  • Any setup steps they should complete

​
Role-Based Workflows

  • Design Team
  • Product Team
  • Cross-Functional
Typical setup:
  • Lead Designer: Admin (manages design system, reviews)
  • Product Designers: Editor (creates features, components)
  • Design Interns: Viewer → Editor after training
Collaboration pattern:
  1. Lead uploads/maintains design system
  2. Designers create features using established patterns
  3. Peer review through comments and suggestions
  4. Lead approves final designs for development

​
Onboarding New Team Members

When someone joins your Figr project:
1

Account Setup

New member receives:
  • Email invitation with project link
  • Instructions to create Figr account
  • Welcome message with project context
They need to:
  • Click invitation link
  • Create account or sign in
  • Complete basic profile setup
2

Project Orientation

Share this checklist with new members:
3

Role-Specific Training

Focus areas:
  • How Figr learns from existing designs
  • Using product context for AI assistance
  • Maintaining design system consistency
  • Advanced editing and refinement tools
Suggested first task: “Redesign our settings page using Figr”
Focus areas:
  • Creating wireframes and user flows
  • Using real data and constraints
  • Collaborative spec creation
  • Stakeholder presentation features
Suggested first task: “Create a new feature concept”
Focus areas:
  • Technical feasibility validation
  • Component mapping and code export
  • Implementation-ready specifications
  • Integration with development workflow
Suggested first task: “Review a design for implementation complexity”

​
Managing Team Access

  • Active Members
  • Pending Invitations
  • Access Logs
Team management dashboard:
Team management interface showing member list with roles and actions
Available actions:
  • Change member roles
  • Resend invitations
  • Suspend/reactivate access
  • Remove team members
  • View activity history

​
Collaboration Best Practices

Clear Communication

Establish norms:
  • Use @mentions for urgent feedback
  • Tag designs with status (Draft/Review/Final)
  • Regular check-ins on shared projects
  • Clear naming conventions for designs

Knowledge Sharing

Build team memory:
  • Document design decisions
  • Share user research insights
  • Upload relevant product context
  • Cross-train on different aspects

​
Effective Comment Workflows

1

Structured Feedback

Use consistent comment formats:
🔴 Critical: Blocks implementation
🟡 Suggestion: Nice to have improvement  
🟢 Approval: Ready to implement
❓ Question: Need clarification
2

Actionable Comments

Good comment examples:✅ “Move CTA above fold - our analytics show 40% drop in conversion below 600px”
✅ “Use $color-primary-600 instead of this blue to match design system”
✅ “Consider loading state - this API call takes 3-5 seconds”Avoid vague feedback: ❌ “This doesn’t look right”
❌ “Make it better”
❌ “I don’t like this color”
3

Resolution Process

Comment lifecycle:
  1. Feedback provided with clear action
  2. Designer implements or responds with questions
  3. Reviewer marks as resolved or continues discussion
  4. Final approval before implementation

​
External Collaboration

  • Client Access
  • Contractor Integration
For external reviewers:
  • Create time-limited viewer access
  • Share specific designs, not entire project
  • Watermark exports if needed
  • Track external user activity
Setup:
Email: client@external.com
Role: Viewer (time-limited)
Access: Specific designs only
Expires: 30 days

Start Your First Design

Now that your team is set up, experience Figr’s product-aware design capabilities.First Design Tutorial →
⌘I