New BETA feature! - Organisations!

For a long time, FoxStock has relied on manually assigned permission sets for stockpiles and networks. While this system has offered fine-grained control, it has also placed a heavy burden on officers managing dozens — sometimes hundreds — of assets. As organisations scale, the current approach simply doesn’t keep up.

Today, we are excited to announce a major milestone in FoxStock’s evolution:

Organisations

Organisations introduce a new, scalable way to structure teams, assign permissions, and manage logistics assets. They are powerful, flexible entities that unify stockpiles, networks, users, and roles into a clear and maintainable hierarchy — drastically reducing the complexity of permission management.

This new system lays the foundation for cleaner workflows, better onboarding, and more reliable logistics collaboration.

Why organisations?

Managing permissions asset-by-asset doesn’t scale. Officers must manually configure access for every new stockpile and network, and every new team member must be added to countless permission sets. It works, but it doesn’t grow.

Organisations solve this problem by:

• Offering centralised permission management
• Allowing teams to define roles with built-in organisation and asset permissions
• Automatically propagating permissions to all organisation assets
• Reducing repetitive work for officers and logisticians
• Creating a foundation for future systems like permission profiles

Organisations are the missing link between granular permissions and true operational scalability.

What are organisations?

Organisations are top-level entities — similar to stockpiles, networks, and users — that group assets and define how teams interact with them. They bring clarity and structure to permission management by acting as the authoritative source for roles, access, and membership.

Ownership

An organisation is always owned by a single user, who permanently retains:

• MANAGE permissions
• A special DELETE action exclusive to owners

Only the owner can delete an organisation, and deletion is irreversible.

Organisation permissions

Organisation-level permissions define who can manage the organisation itself:

• READ — View organisation metadata and its assets
• WRITE — Add or remove stockpiles and networks from the organisation
• MANAGE — Add or remove users and roles

Users cannot remove the owner, but they can remove themselves if needed.

Asset permissions

Asset permissions determine what members can do with the organisation’s stockpiles and networks. They mirror existing FoxStock asset permissions, but are applied automatically to all assets the organisation owns:

• READ — View the asset and its contents. Members can inspect stockpile inventories and network structures.
• WRITE — Modify the asset’s settings and metadata. This includes renaming the asset or adjusting its description and location.
• SUBMIT_ITEMS — Update stockpile inventories. Members can submit new quantities, add items, or record item removals.
• MANAGE — Full administrative control over the asset. This includes modifying permissions and, where applicable, deleting the asset.

These permissions cascade down to every asset the organisation owns. Unless an individual asset explicitly restricts access, organisational roles define the default permissions.

Roles

Roles let managers define groups of users and assign them both organisation permissions and asset permissions in a single place. Roles can be based on:

• Discord roles
• Existing user groups
• Individual users

Roles make permission management predictable and scalable. When a new asset is added to the organisation, it automatically inherits all role-based permissions.

Assets in organisations

Stockpiles and networks can belong to multiple organisations, though this is not recommended due to UI clutter. When an asset belongs to an organisation, its permission tab displays the organisation’s roles and their assigned permissions. These entries are non-editable and non-deletable, since they originate from the organisation’s configuration.

If needed, managers can override a role’s inherited permissions by creating a local permission entry using the same selector. When this happens, the inherited entry is hidden and the local rule takes priority.

What’s next?

Organisations mark a major step forward for FoxStock. Over time, they will become the foundation for:

• Permission Profiles
• Advanced team structures
• Better onboarding workflows
• Cleaner recommendation routing between organisational assets

With your feedback, we’ll refine and expand the feature to better support regiments, clans, logistics teams, and large-scale operations. If you have suggestions or run into issues, please let us know on our Discord or GitHub.

Thank you

This feature wouldn’t exist without the incredible FoxStock community. Your use cases, suggestions, and real-world logistics challenges directly shaped Organisations into what they are today. We’re excited to continue building the tools that keep your war machine running.

Thank you for being part of this journey!