Organizations & Team Management: Complete Guide | Nife Docs

Comprehensive guide to setting up and managing organizations, teams, members, workloads, and secrets in Nife.

Getting Started with Organizations#

Organize your team and resources efficiently:

  1. Organizations Overview - Create and manage organizations
  2. Managing Members - Invite members and assign roles
  3. Managing Workloads - View and manage all workloads
  4. Organizational Secrets - Manage sensitive data
  5. Migrating Organizations - Move resources between organizations

Organization Features#

👥 Team Management#

  • Create multiple organizations
  • Invite team members
  • Assign roles and permissions
  • Manage access control
  • Admin, Member, and Viewer roles

📦 Workload Organization#

  • View all workloads across organization
  • Monitor application status
  • Manage deployments
  • Scale applications
  • Track resource usage

🔐 Secrets Management#

  • Store API keys securely
  • Manage credentials
  • Organize sensitive data
  • Control access to secrets
  • Encrypted storage

🔄 Organization Migration#

  • Move resources between organizations
  • Consolidate teams
  • Reorganize structure
  • Transfer workloads
  • Maintain continuity

Key Concepts#

Organizations#

Logical grouping of resources, members, and workloads. Each organization:

  • Has its own members and access control
  • Contains applications and deployments
  • Has its own secrets and credentials
  • Can be isolated or shared

Roles#

Control what members can do:

Admin

  • Full control of organization
  • Invite/remove members
  • Manage all resources
  • Delete organization
  • Access all secrets

Member

  • Create and manage applications
  • Manage workloads
  • Access secrets
  • Cannot invite members
  • Cannot delete organization

Viewer

  • Read-only access
  • View applications
  • View workloads
  • Cannot modify anything
  • Cannot invite members

Workloads#

All running applications and services:

  • Applications (deployed code)
  • Deployments (versions)
  • Instances (containers)
  • Jobs (scheduled tasks)

Secrets#

Secure storage for sensitive data:

  • API keys and tokens
  • Database passwords
  • Service credentials
  • Configuration values
  • License keys

Common Workflows#

Set Up a New Organization#

  1. Create Organization → Go to Organizations, click Create
  2. Invite Members → Add team members with appropriate roles
  3. Create Applications → Deploy your first workload
  4. Add Secrets → Store sensitive credentials
  5. Monitor Workloads → Track status and metrics

Add Team Member#

  1. Invite → Go to Organization, click Invite Member
  2. Choose Role → Select Admin, Member, or Viewer
  3. Accept → Member receives invitation
  4. Access → Member can now access organization

Manage Organizational Secrets#

  1. Create → Add Secret with name and value
  2. Reference → Use in applications as $SECRET_NAME
  3. Update → Edit secret value when needed
  4. Delete → Remove unused secrets
  5. Audit → Monitor secret access

Migrate Organization#

  1. Prepare → Inform team and backup data
  2. Migrate → Click Migrate on organization card
  3. Select Destination → Choose target organization
  4. Confirm → Review and confirm migration
  5. Verify → Check all resources moved successfully

Frequently Asked Questions#

Q: How many organizations can I create?#

A: Create as many organizations as needed. Organize by team, project, or environment.

Q: What's the difference between Member and Viewer?#

A: Members can create and modify resources. Viewers can only read/view.

Q: Can I change member roles after inviting?#

A: Yes, click the role dropdown and select new role.

Q: Where do I store API keys?#

A: Use Organizational Secrets to securely store keys and credentials.

Q: Can I move applications between organizations?#

A: Yes, use the migrate feature to move resources between organizations.

Q: Are secrets encrypted?#

A: Yes, all secrets are encrypted in storage and transmission.

Q: What happens when I delete an organization?#

A: All resources in that organization are deleted. This cannot be undone.

Q: Can I have different members in different organizations?#

A: Yes, each organization has its own members and access control.

Q: How do I monitor organization-wide activity?#

A: View the Workloads tab to see all applications and deployments.

Q: Can I share secrets between organizations?#

A: Secrets are organization-specific. Create the same secret in each org if needed.

Best Practices#

Organization Design#

  • ✅ Create separate orgs for different teams
  • ✅ Use clear, descriptive organization names
  • ✅ Organize by environment (dev, staging, prod)
  • ✅ Organize by project or product
  • ✅ Keep related workloads together

Member Management#

  • ✅ Follow principle of least privilege
  • ✅ Assign appropriate roles based on job
  • ✅ Review members regularly
  • ✅ Remove inactive members
  • ✅ Document access decisions

Secrets Management#

  • ✅ Use clear naming conventions
  • ✅ Store only sensitive data as secrets
  • ✅ Rotate credentials regularly
  • ✅ Limit who can access secrets
  • ✅ Audit secret usage

Workload Organization#

  • ✅ Use meaningful application names
  • ✅ Tag workloads for filtering
  • ✅ Group by environment
  • ✅ Monitor resource usage
  • ✅ Plan scaling needs

Team Collaboration#

  • ✅ Communicate access changes
  • ✅ Document organization structure
  • ✅ Update team on migrations
  • ✅ Share knowledge about setup
  • ✅ Maintain access records

Organization Structure Examples#

By Team#

Org: Frontend Team
├─ Web application
├─ Mobile app
└─ Design tools
Org: Backend Team
├─ API services
├─ Database services
└─ Cache layer
Org: DevOps Team
├─ CI/CD pipelines
├─ Monitoring tools
└─ Infrastructure

By Environment#

Org: Development
├─ Dev database
├─ Dev application
└─ Test servers
Org: Staging
├─ Staging database
├─ Staging application
└─ Load testing
Org: Production
├─ Production database
├─ Production application
└─ Backup services

By Project#

Org: Project Alpha
├─ Alpha backend
├─ Alpha frontend
└─ Alpha database
Org: Project Beta
├─ Beta backend
├─ Beta frontend
└─ Beta database

Quick Links by Role#

For Administrators#

For Team Leads#

For Developers#

For Operations#

Related Documentation#

Application Management#

Team & Access#

Infrastructure#

Support & Resources#

Need Help?

What's Next?#

Ready to organize your team?

  1. Create Organization - 5 minutes
  2. Invite Members - 10 minutes
  3. Deploy Application - 15 minutes
  4. Add Secrets - 5 minutes

Estimated total time: 35 minutes to complete team setup!