Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Greens-Organization/pz-packs/llms.txt

Use this file to discover all available pages before exploring further.

​
Team Collaboration

PZ Packs supports collaborative modpack management through a flexible team member system. Add team members to your modpacks, assign granular permissions, and work together to maintain your mod collections.

​
Overview

Collaboration features allow multiple users to work on the same modpack with different levels of access control.

Email-Based Invites

Add team members using their email address - they must have a PZ Packs account.

Granular Permissions

Control exactly what each member can do with fine-grained permission settings.

Owner Controls

Modpack owners have full control and can manage all members and permissions.

Member Tracking

View all members, their permissions, and when they were added to the modpack.

​
Adding Team Members

Invite users to collaborate on your modpack.
1

Open Your Modpack

Navigate to the modpack details page for the modpack you want to share.
2

Access Members Section

Click on “Members” or the team icon to view the members list.
3

Click Add Member

Click the “Add Member” button to open the invitation dialog.
4

Enter Email Address

Type the email address of the user you want to add.
The user must already have a PZ Packs account with this email address.
5

Assign Permissions

Select which permissions to grant the new member (see Permission System below).
6

Send Invitation

Click “Add Member” to add them to the modpack.

​
Requirements

Only the modpack owner can add members. The manager-members permission is required, which is exclusive to owners.
  • The invitee must have an active PZ Packs account
  • The email must exactly match their account email
  • You cannot add the same user twice to a modpack

​
Removing Team Members

Remove members who no longer need access to the modpack.
1

View Members List

Navigate to the members section of your modpack.
2

Select Member to Remove

Find the member you want to remove from the list.
3

Click Remove

Click the remove button next to their name.
4

Confirm Removal

Confirm the removal in the dialog box.
Removing a member immediately revokes their access to the modpack. They will no longer be able to view or modify it unless they are re-added.

​
Removal Notes

  • Members are soft-deleted (marked as isActive: false)
  • Member records are preserved in the database for audit purposes
  • You cannot remove yourself if you’re the owner
  • Only owners can remove members

​
Permission System

PZ Packs uses a granular permission system to control what team members can do.

​
Available Permissions

Permissions are stored as an array of action strings. Here are the permissions available in PZ Packs:
Permission: readAllows:
  • View the modpack details
  • See the modpack in “My Modpacks” list
  • Access modpack information
Required for: Basic access to a private modpack
All members automatically receive the read permission when added.
Permission: updateAllows:
  • Edit modpack name and description
  • Update avatar URL and Steam URL
  • Change public/private visibility
Required for: Modifying modpack metadata
Granting update permission allows members to make the modpack public or private.
Permission: add-modAllows:
  • Add new mods to the modpack by Workshop ID or Steam URL
  • Trigger fetching of mod information from Steam
Required for: Growing the modpack’s mod collection
Permission: remove-modAllows:
  • Remove mods from the modpack
  • Clean up unwanted or conflicting mods
Required for: Curating the mod list
Removing a mod only removes it from the modpack, not from the PZ Packs database.
Permission: importAllows:
  • Import mods from Steam Collections
  • Check import job status
Required for: Bulk adding mods via Steam Collection import
Permission: exportAllows:
  • Request server file generation
  • Download generated server configuration files
  • View export configuration
Required for: Generating server configuration files
Permission: archiveAllows:
  • Archive (soft delete) the modpack
Required for: Removing the modpack from active use
This is a destructive action. Only grant this permission to trusted team members.
Permission: manager-membersAllows:
  • Add new members to the modpack
  • Remove existing members
  • View member list
Required for: Team management
This permission is owner-only and cannot be granted to regular members. Only the modpack owner can manage members.

​
Permission Assignment

When adding a member, you can select which permissions they receive: 
// Example permission array for a member
permission: [
  "read",
  "add-mod",
  "remove-mod",
  "export"
]

​
Default Permission Sets

While PZ Packs allows custom permission combinations, here are some common permission sets:
Permissions: ["read"]Can only view the modpack and its mods. Cannot make changes.Use case: Sharing modpack information without allowing modifications.

​
Member Roles

While PZ Packs doesn’t have formal “roles,” there are two functional levels:

Owner

  • One owner per modpack
  • Cannot be changed or transferred
  • Has all permissions automatically
  • Can manage members
  • Can archive the modpack
The owner is the user who created the modpack.

Member

  • Multiple members allowed
  • Permissions assigned individually
  • Cannot manage other members
  • Can be removed by owner
  • Access controlled by permission array
Members are users added by the owner.

​
Viewing Members

See who has access to your modpack and what they can do.

​
Member List Display

The members section shows:
  • Member avatar: Profile picture (if set)
  • Name: Display name or email
  • Permissions: What actions they can perform
  • Added date: When they were added to the modpack
  • Status: Active or inactive

​
Member Avatars

Members are displayed with avatar buttons that show:
  • Profile picture thumbnail
  • Tooltip with full name and email
  • Visual indication of member count
If there are more members than can be displayed, a “Show Remaining” option appears to view the full list.

​
Access Control Flow

How permissions are checked when members perform actions:
1

User Requests Action

A member attempts to perform an action (e.g., add a mod).
2

Authentication Check

The system verifies the user is logged in and has an active session.
3

Ownership Check

If the user is the modpack owner, they automatically have all permissions. Process ends here.
4

Membership Check

The system checks if the user is a member of the modpack and if their membership is active (isActive: true).
5

Permission Check

The system verifies the required permission is in the member’s permission array.
6

Action Allowed or Denied

  • If all checks pass: Action is allowed
  • If any check fails: Action is denied with appropriate error message

​
Permission Enforcement

Permissions are enforced at multiple levels:
  1. API Routes: Server-side permission checks before executing actions
  2. UI Components: Buttons and features are hidden if user lacks permission
  3. Database Queries: User context filters data access
UI hiding is not a security measure - permissions are always enforced server-side. The UI simply provides a better user experience by hiding unavailable options.

​
Sharing Modpacks

While PZ Packs doesn’t have a “share link” feature, there are several ways to share modpacks:

​
Public Modpacks

1

Make Modpack Public

Edit your modpack and toggle the “Public” switch to on.
2

Share the URL

Copy your browser’s URL from the modpack page and share it.Example: https://pzpacks.com/modpacks/abc-123
3

Others Can View

Anyone with the link can view the modpack, its mods, and export server files (if authenticated).

​
Private Modpacks with Members

1

Keep Modpack Private

Do not enable the “Public” setting.
2

Add Members

Add specific users as members with appropriate permissions.
3

Members Get Access

Members can view and interact with the modpack based on their permissions.
Public modpacks appear in the public modpack listings and can be discovered by anyone. Private modpacks only appear to the owner and members.

​
Use Cases

Scenario: Multiple admins manage a game server’s mod collection.Setup:
  • Owner: Server owner or head admin
  • Members: Co-admins with read, add-mod, remove-mod, export permissions
Benefits:
  • Multiple people can update the mod list
  • All admins can export server configs
  • Central owner maintains control
Scenario: A team curates a public modpack for community use.Setup:
  • Owner: Lead curator
  • Members: Contributing curators with read, add-mod, remove-mod
  • Public: Enabled for community access
Benefits:
  • Multiple curators collaborate on the collection
  • Community can view and use the modpack
  • Quality control maintained by owner
Scenario: Developers test mod compatibility in a shared environment.Setup:
  • Owner: Lead developer
  • Members: Testers with read, export permissions
Benefits:
  • Testers can export and test configurations
  • Lead developer controls mod list
  • Prevents accidental changes during testing
Scenario: Share a modpack configuration without allowing changes.Setup:
  • Owner: Modpack creator
  • Members: Viewers with only read permission
  • Alternative: Make modpack public
Benefits:
  • Others can see the mod list
  • No risk of accidental modifications
  • Owner maintains full control

​
Best Practices

  • Start with minimal permissions and add more as needed
  • Document why each member has specific permissions
  • Review permissions periodically
  • Remove inactive members promptly
  • Reserve archive permission for fully trusted members only
  • Establish guidelines for modpack changes
  • Use external tools (Discord, Slack) for coordination
  • Document major mod additions/removals
  • Coordinate before making significant changes
  • Test changes before deploying to production servers
  • Keep the member list up to date
  • Remove members when they leave the team
  • Use descriptive member names/emails for easy identification
  • Periodically audit who has access
  • Have a backup owner contact for emergencies
  • Allow members to maintain their own export configs
  • Document the “official” export configuration
  • Test exports before deploying to servers
  • Keep a record of working configurations
  • Coordinate export changes with the team

​
Troubleshooting

Error: “User not found” or “Invalid email”Solutions:
  • Verify the user has a PZ Packs account
  • Check email spelling and case
  • Ensure you’re using the email they registered with
  • Ask the user to confirm their account email
Error: “Permission denied” or action button is hiddenSolutions:
  • Check the member’s permission array
  • Verify the required permission is granted
  • Ensure the member’s account is still active
  • Check if they’re logged in with the correct account
Error: “Member already exists”Solutions:
  • Check if the user is already in the member list
  • Look for inactive members (soft-deleted)
  • Contact support if you need to reactivate a removed member

​
Limitations

Current limitations of the team collaboration system:
  • No role templates or presets (permissions are manually assigned)
  • Cannot transfer ownership of a modpack
  • No notification system for modpack changes
  • Member activity is not tracked in the UI
  • No “pending invitation” state (users must have accounts first)

​
Next Steps

Modpack Management

Learn how to create and organize modpacks

Server Configuration

Export server files with team member configurations

Mods

Add and manage mods collaboratively

API Reference

Programmatically manage members via API

Build docs developers (and LLMs) love

Get started for freeTalk to us