Team Management

Manage your organization's team members, roles, and access controls at both organization and workspace levels.

Effective team management is crucial for maintaining security and ensuring the right people have the appropriate access to your organization's data integration workflows. Precog provides a two-tiered access control system: organization-level roles and workspace-level permissions.

Accessing Team Management

All team management functions are available in the Organization Team section of your Precog workspace. You can access this directly through the left-hand navigation menu or by clicking here to go to Organization Team.

Understanding Access Control

Precog uses a two-level access control system:

  1. Organization Level - Controls team membership and organization-wide permissions
  2. Workspace Level - Controls read/write access to individual workspaces

Who Can Manage Teams?

Owners and Admins are able to control team membership at the organization level, including inviting new members, assigning roles, and removing team members.

Organization-Level Roles

At the organization level, there are four distinct roles that determine what members can do:

1. Owner

Full system access - Owners have unrestricted access to all organization functions.

Capabilities:

  • Manage all team members (add, remove, change roles)
  • View and manage all billing information
  • Access all workspaces with full permissions
  • Configure organization-wide settings
  • Transfer ownership to another member

Use Case: Organization leaders, primary administrators, or business owners who need complete control.

2. Admin

Team management without billing access - Admins can control who belongs to the organization but cannot view or manage billing data.

Capabilities:

  • Invite new team members
  • Remove team members
  • Change member roles (except Owner)
  • Manage organization settings
  • Access workspaces based on workspace permissions

Cannot:

  • View billing information
  • Manage payment methods
  • Access invoices or usage reports

Use Case: Team leads, project managers, or technical administrators who manage people but don't handle finances.

3. Billing User

Financial visibility without team control - Billing users can see all billing data but cannot change team membership.

Capabilities:

  • View all billing information
  • Access invoices and payment history
  • Monitor usage and costs
  • Update payment methods
  • Access workspaces based on workspace permissions

Cannot:

  • Invite or remove team members
  • Change member roles
  • Manage organization settings

Use Case: Finance team members, accountants, or business analysts who need visibility into costs without people management responsibilities.

4. Regular Member

Standard access - Regular members can work within the organization but have no administrative capabilities.

Capabilities:

  • Access assigned workspaces
  • Work with data sources and destinations
  • Create and manage schedules (if granted workspace write access)

Cannot:

  • View billing information
  • Manage team membership
  • Change organization settings
  • Invite new members

Use Case: Data engineers, analysts, and developers who need to work with data integration workflows.

Workspace-Level Permissions

In addition to organization-level roles, each member can have different permissions for individual workspaces. This provides fine-grained access control for different environments or projects.

Read Access

Members with read access can view workspace configuration but cannot make changes:

  • View sources and their configurations
  • View destinations and their configurations
  • See schedules and their settings
  • Monitor execution history
  • View datasets

Cannot:

  • Create or modify sources
  • Create or modify destinations
  • Create or edit schedules
  • Delete or change existing configurations

Write Access

Members with write access can make changes to the workspace:

  • All read access capabilities
  • Create, modify, and delete sources
  • Create, modify, and delete destinations
  • Create, modify, and delete schedules
  • Configure dataset settings
  • Trigger manual syncs

Example: Production Environment Control

A common use case is restricting write access to production workspaces:

Scenario: You have a production workspace that syncs critical business data to your data warehouse.

Setup:

  • Owners/Admins - Write access (can make emergency changes)
  • Senior Engineers - Write access (can deploy to production)
  • Junior Engineers - Read access (can view configuration and learn)
  • Analysts - Read access (can see what data is available)

This ensures that critical production workflows are protected while still allowing visibility across the team.

Core Team Management Functions

Inviting Team Members

Add new team members to your organization:

  1. Navigate to Organization Team in the left sidebar
  2. Click "Invite Member"
  3. Enter the email address of the person you want to invite
  4. Select their organization role (Owner, Admin, Billing User, or Member)
  5. Send the invitation - they'll receive an email with instructions to join

After joining, you can assign workspace-level permissions individually for each workspace they need access to.

Managing Team Members

Once team members have joined, you can manage their access:

  • View all current members and their organization roles
  • Update member roles as organizational needs change
  • Adjust workspace permissions for individual workspaces
  • Remove members who no longer need access

Managing Pending Invitations

Keep track of outstanding invitations and take action when needed:

Resending Invitations

If someone didn't receive their invitation or it expired:

  1. Find the pending invitation in the team management interface
  2. Click "Resend" to send a fresh invitation email
  3. Confirm the email address is correct before resending

Revoking Invitations

If you need to cancel a pending invitation:

  1. Locate the pending invitation in your team list
  2. Click "Revoke" or "Cancel" to prevent the invitation from being used
  3. Confirm the action - this permanently removes the invitation

Common Reasons to Revoke:

  • Email address was entered incorrectly
  • Person is no longer joining the organization
  • Role or permissions have changed significantly
  • Security concerns about the invitation

Need help with team management? Visit our Getting Help page for support options including team setup assistance, permission guidance, and technical troubleshooting.