Overview

FutureFund Connect uses a role-based system to manage responsibilities and access across your PTA hierarchy. Roles represent defined responsibilities within each PTA level, and tasks and approvals can be assigned to roles rather than specific individuals. When a task is assigned to a role, any user holding that role at the relevant entity receives it.

The permission system controls who can see and do what. It has two types — explicit and implicit — that work together to ensure the right people have the right access.

How to Understand Permissions

1. Explicit permissions are granted directly to a user for a specific entity (state, district, council, or unit). A user can have explicit access to more than one entity.
2. Implicit permissions are inherited based on the PTA hierarchy:
   • Council-level access grants access to the council and all of its units.
   • District-level access grants access to the district, all of its councils, and all of their units.
   • State-level access grants access to everything in the state.
3. To check a user’s access, navigate to the entity and open the Permissions section.
4. To grant access, add the user to the appropriate entity’s permission list.

Additional Features

• Tasks and approvals route to roles, not individuals — if a board member changes mid-year, the new person in that role automatically receives pending tasks.
• Users can hold roles at multiple entities simultaneously.
• Permission changes take effect immediately.
• Higher-level permissions automatically cascade down through the hierarchy without additional configuration.

Tips

• Use implicit permissions strategically. Granting access at the district level is more efficient than adding a user to every council and unit individually.
• When a user reports they cannot see an entity, check whether they have either explicit access to that entity or implicit access from a higher level.
• Remember that explicit permissions to one entity do not grant access to other entities at the same level. A user with access to Council A does not automatically get access to Council B.