Organizations

This guide explains how to create and manage organizations in EchoPastel to organize your teams and projects.

What is an organization?

An organization in EchoPastel is a workspace that groups:

• Members: People who are part of the organization
• Echos: Feedback projects associated with the organization
• Permissions: Access and modification rules

Organizations allow you to:

• Separate projects by client or team
• Manage permissions centrally
• Organize your work in a structured way

Create an organization

Creation steps

1. Access the "Organizations" section from your dashboard
2. Click on "Create an organization" or "New organization"
3. Enter the information:
   • Organization name: A descriptive name (e.g., "Client ABC", "Design Team")
   • Slug: A unique identifier (automatically generated or customized)
4. Click on "Create"

Naming best practices

• Use clear and descriptive names
• Prefer names that reflect usage (client, team, project)
• Avoid special characters in slugs

Manage members

Invite members

To add members to your organization:

1. Open your organization
2. Go to the "Members" section
3. Click on "Invite member"
4. Enter the person's email address
5. Set the role (see Roles section below)
6. Click on "Send invitation"

The invitee will receive an email with a link to join the organization.

Roles and permissions

EchoPastel offers different roles with different access levels:

Owner

• Full access to the organization
• Can modify all settings
• Can delete the organization
• Can manage all members

Administrator

• Can manage members (invite, remove)
• Can modify organization settings
• Can create and manage all Echos
• Cannot delete the organization

Member

• Can create Echos
• Can annotate and collaborate
• Limited access to settings
• Cannot manage members

Remove a member

To remove a member from the organization:

1. Open your organization
2. Go to the "Members" section
3. Find the person in the list
4. Click on "Remove" or "Delete"

Note: Removing a member does not delete their existing annotations, but they will no longer have access to new Echos in the organization.

Manage Echos

Create an Echo in an organization

When creating an Echo, you can choose the organization:

1. Create a new Echo as usual
2. Select the organization from the dropdown list
3. The Echo will be associated with this organization

View organization Echos

All Echos in an organization are visible in:

• The organization dashboard
• The Echo list filtered by organization
• Search results

Permissions on Echos

Permissions on Echos depend on:

• The role in the organization
• Specific permissions of the Echo
• The owner status of the Echo

Multi-organizations

Manage multiple organizations

You can be a member of multiple organizations:

• Switch organizations: Use the organization selector in the menu
• View all your organizations: Access the list from your profile
• Create new organizations: No limit (depending on your plan)

Use cases

Multi-organizations are useful for:

• Managing different clients: One organization per client
• Separating teams: One organization per team
• Isolating projects: One organization per major project

Organization settings

General settings

You can modify:

• Organization name
• Slug (unique identifier)
• Description (optional)

Billing settings

Depending on your configuration:

• Organizations can have their own billing
• Or billing can be at the user level

Note: Check the pricing page for more information on plans.

Limits by plan

The number of organizations you can create depends on your plan:

• Free plan: 1 organization
• Pro plan: Unlimited organizations
• Lifetime plan: Unlimited organizations
• Enterprise plan: Unlimited organizations

Best practices

Organization by client

Create one organization per client to:

• Separate projects
• Manage permissions by client
• Facilitate billing

Organization by team

Create one organization per team to:

• Isolate internal projects
• Manage permissions by team
• Organize work

Consistent naming

Use a consistent naming system:

• Format: [Type] - [Name] (e.g., "Client - ABC Corp", "Team - Design")
• Avoid generic names
• Document the usage of each organization

Granular permissions

Access control

Organizations allow granular access control:

• At organization level: Who can view and modify the organization
• At Echo level: Who can annotate and modify each Echo
• At annotation level: Who can view and reply to annotations

Security

Organizations ensure:

• Data isolation: One organization's data is not visible to others
• Access control: Only authorized members can access
• Audit trail: All actions are traceable

Next steps

• Discover collaboration - Share and collaborate efficiently
• Create your first Echo - Start using organizations
• Explore features - Discover all possibilities