What is a Project?
A project in Swig represents an application or product that uses the Swig protocol. Each project has:- Members with different roles and permissions
- A subscription that determines available features
- API keys for programmatic access
- Policies defining wallet permissions
- Paymasters for transaction sponsorship
Key Features
Team Collaboration
Projects support multiple members with role-based access control:Subscription Tiers
Each project has a subscription that determines available features:Automatic Setup
When you sign up for Swig:- A project is automatically created for you
- You’re assigned as the Owner
- A FREE subscription is activated
- You can start creating API keys and policies immediately
Project Structure
Getting Started
Create Project
Set up a new project for your application
Manage Members
Invite team members and manage roles
Subscriptions & Billing
Upgrade your plan and manage billing
Best Practices
Project Naming
Choose a clear, descriptive name for your project:- Use your company or application name
- Keep it recognizable for team members
- Avoid special characters
Role Assignment
Follow the principle of least privilege:- Give Owner role only to key decision-makers
- Use Admin for team leads who need member management
- Assign Member role for developers
- Use Billing for finance team members who only need billing access
Multiple Projects
You can be a member of multiple projects:- Use separate projects for different applications
- Keep production and development environments separate
- Maintain clear boundaries between client projects
Next Steps
- Create a project for your application
- Invite team members to collaborate
- Choose a subscription that fits your needs