Team Collaboration

ULink lets you invite team members to collaborate on projects. Share access with colleagues so everyone can create and manage links.

What you'll learn

• Inviting team members to your project
• Understanding Owner and Admin roles
• Managing team access

Team structure

ULink teams work at the project level:

Your Project
├── Owner: You
└── Admins: Sarah, Mike, Jane

Each project has one owner and can have multiple admins. Everyone with access can create and manage links.

Roles and permissions

Owner

The project creator with full control:

• Manage all project settings
• Invite and remove team members
• Transfer ownership to another user
• Delete the project
• All admin permissions

Each project has exactly one owner. To change ownership, the current owner must transfer it to an admin.

Admin

Team members with full project access:

• Create and edit all links
• View all analytics
• Invite new team members
• Manage project settings
• Manage domains and API keys

Admins can do everything except delete the project or transfer ownership.

Inviting team members

To invite someone to your project:

1. Go to Project Settings → Team
2. Click "Invite Member"
3. Enter their email address
4. Send the invitation

They'll receive an email with a link to join. If they don't have a ULink account, they'll create one during the process.

Managing team members

Changing roles

The owner can promote an admin to owner (transferring ownership) or adjust team composition as needed.

Removing team members

When someone leaves your team:

1. Go to Project Settings → Team
2. Find the team member
3. Click "Remove"

Their access is revoked immediately. Links they created remain in the project.

Best practices

Invite only who needs access

Keep your team list focused. It's easier to add people than to remember to remove them later.

Use descriptive API key names

When team members create API keys, use clear names:

✓ "iOS Production SDK"
✓ "Marketing Automation - HubSpot"
✗ "Key 1", "Test", "asdf"

Document your conventions

Write down your naming conventions and link organization patterns. New team members should understand the system from day one.

Review access periodically

Check who has access to your projects:

• Remove people who've left the team
• Verify API keys are still needed
• Ensure the right person is the owner

Quick recap

• Teams are managed at the project level
• Two roles: Owner (one per project) and Admin
• Invite team members via email
• All team members can create and manage links
• Review access regularly