Team Management
Invite people to help manage your store with permissions that control exactly what each person can see and do.
Overview
You add team members by email; each one gets a role you define from scratch by picking permissions area by area. Store owners always have full access — permissions only apply to invited members, not to you.
Inviting a member
Go to Dashboard > Team and click Invite Member. Enter their email (they must already have a FluxStore account), tick the permissions you want them to have, and click Invite. They appear in your team list once they accept the invitation.
Permission levels
Every permission area is independently set to any combination of four access levels:
| Level | What it allows |
|---|---|
| View | Read-only access. They can see records in this area but not change anything |
| Edit | Create and modify records. Implies View |
| Credit | Money-moving actions like issuing refunds. Used by a few specific areas; on most areas it does nothing extra |
| Delete | Permanently remove records. Implies View |
Tick the boxes individually per area when inviting or editing a member.
Grant Delete sparingly. Deleted records (packages, categories, customers, orders) generally cannot be recovered.
Permission areas
FluxStore has 29 permission areas. The labels below match what you’ll see on the team-member edit screen.
| Area | What it covers |
|---|---|
| Stores | Store settings, branding, configuration |
| Packages | Products sold on the storefront |
| Categories | Display categories that group packages |
| Coupons | Discount codes |
| Sales | Automatic sales and promotions |
| Gift Cards | Gift card codes and balances |
| Orders | Customer orders |
| Bans | Player bans |
| Referrals | Referral tracking |
| Payment Gateways | Stripe, PayPal, and other gateway configuration |
| Servers | Connected Minecraft servers |
| Customization | Storefront appearance, themes, layout editor |
| Email Templates | Transactional email templates |
| Modules | Storefront modules (recent payments, donation goal, etc.) |
| Webhooks | Outgoing webhook endpoints and event subscriptions |
| Reports | Analytics dashboards |
| Assets | Image and file uploads |
| Custom Templates | Liquid template editor and asset uploads |
| Issue Refunds | Permission to refund orders (requires Orders permission too) |
| Show Customer PII | View customer emails, names, and other personal info |
| Resend Commands | Retry failed delivery commands (requires Orders permission too) |
| Teams | Team-member management |
| Global Commands | Commands that run alongside every order |
| Customers | Customer list and individual customer pages |
| Custom Pages | Custom storefront pages (About, FAQ, etc.) |
| Discord | Discord bot integration and role mappings |
| Subscriptions | Recurring subscription orders |
| Tickets | Support ticket management |
| Checkout | Hosted checkout sessions (used by the API for headless checkouts) |
Issue Refunds and Resend Commands also need the Orders permission to do anything. Without at least View on Orders, the member can’t find an order to refund or resend.
Example role setups
Support agent. View on Orders, Customers, and Show Customer PII. Edit on Bans and Resend Commands so they can retry failed deliveries and ban problem players. No access to anything financial.
Product manager. View + Edit on Packages, Categories, Sales, Coupons, and Gift Cards. View on Reports so they can see how products are performing.
Developer. View + Edit on Webhooks, Servers, Modules, and Custom Templates. Useful for someone who’s integrating with FluxStore or building a custom storefront design.
Customer-facing support. View on Orders, Customers, Tickets, Show Customer PII. Edit on Tickets so they can respond. Edit on Resend Commands so they can fix delivery issues.
Full admin. Every level on every area. Mirrors the owner’s access, but they can still be removed and they can’t transfer store ownership.
Managing team members
Open Dashboard > Team, click a member, change their permissions, and save. Changes take effect on the member’s next page load.
To remove a member, click them and select Remove Member. They immediately lose access to your store dashboard. Their FluxStore account itself isn’t deleted; they can still be invited to other stores.
Security tips
- Least privilege. Grant only what the member actually needs. You can always add more later.
- Audit regularly. Review your team list every few months. Remove anyone who no longer needs access.
- Restrict the sensitive areas. Show Customer PII, Issue Refunds, Payment Gateways, and Teams all grant access to material that can hurt you if misused. Keep these to trusted members.
- Watch Teams carefully. A member with Edit on Teams can change other members’ permissions, including their own. Only give Teams access to people you’d give the keys to the building.