What's changing?
Float is updating how access rights are organized and managed.
We are replacing our fixed access right types—Admin, Manager, and Member—and their associated permissions with custom access roles.
Access roles introduce pre-defined buckets that tailor your ability to see different areas of the product, with granular, individually configurable permissions.
The default access roles replacing the current setup are:
Admin: the default administrative access role for managing company settings, people, projects, and access.
Resource Manager: the default resource planning access role designed for scheduling and viewing people and projects across the team.
Project Manager: the default project management access role tailored for managing owned or granted project work.
Member: the default access role for viewing schedules and logging time.
A new Access rights tab will be added to your Company settings, giving Account Owners one centralized place to view and manage access roles and their permissions. Account Owners can also grant Admins the ability to edit and configure access roles, so day-to-day access management doesn't have to sit with one person.
Will this change affect my team's current permissions?
No. Everyone on your team keeps exactly the same access they have today.
Every single person on your team will keep identical access as they do today. If someone can see budgets right now, they'll still see budgets after the switch. If they can't edit a project right now, that stays true too. Whatever someone can and can't do right now is exactly what they'll be able to do the moment the update lands on your account. You don't need to make any changes before the rollout to preserve your team's current permissions.
Why are we making this change?
More flexible and configurable permissions have been one of our most requested features, particularly from growing teams with more complex access requirements.
Moving to access roles makes it easier to give people the access they need without managing permissions individually. It also gives Account Owners more flexibility to adapt Float's access setup to the way their organization works.
When is this change going live?
The updated access rights experience will begin rolling out in phases starting in mid-
October 2026.
Not all accounts will switch at the same time. You will receive an email and an in-app notification before the update reaches your account. If your account hasn't shifted by October 20th, it will automatically update within the following few weeks.
What happens to our existing access rights?
This update is designed not to disrupt your day-to-day flow. On the day of the update, we will map each person to the default access role that most closely matches their current access: Admin, Resource Manager, Project Manager, or Member. If someone's existing permissions match a default role, they'll simply be assigned to that role.
If their existing permissions don't exactly match a default role, Float will assign the closest role and preserve the differences as person-level overrides. This is intentional: overrides ensure that nobody gains or loses access simply because your account has moved to the new system.
In some cases, someone may be mapped to a role that sits below their previous access level - for example, a Manager might be assigned Member access rights if that's the closest default match. This doesn't mean they've lost access. Any permissions above that role's defaults will be preserved as individual overrides, so they'll continue to see and do exactly what they could before.
You'll be able to identify people with individual permission overrides on the People page. If your company currently has many individually configured permissions, you may see quite a few overrides after the migration. That's expected.
How is this different from the current setup?
In the current system, access rights are fixed, and additional permissions are managed at the individual level. With the new access roles, you get:
Granular control: Permissions are broken down into precise, individual actions, giving you more control over exactly what people can see and do.
*UI subject to change
Custom roles (Pro & Enterprise plans): If you are on a Pro or Enterprise plan, you can also customize the default roles, create brand-new roles from scratch, or duplicate existing roles to tweak them for different groups within your team.
*UI subject to change
What are the default permissions for each access role?
Each access role comes with a defined set of default permissions covering areas like scheduling, time off, projects, finance, time tracking, and company settings. Here's a quick overview:
Admin - full access to people, projects, finance, company settings, and access management.
Resource Manager - can view and schedule all people and projects, and manage time off across the team.
Project Manager - can create and manage projects, log time for project teams, and approve time off for their team.
Member - can view their schedule, log their own time, and manage their own time off.
Full breakdown of what each role can and can't do by default, coming soon. Stay tuned!
📝Note: The Account Owner role cannot be assigned or customized. By default, the person who created the account holds this role. There can only be one Account Owner per team, and ownership can be transferred at any time. Account Owners have full control of the account. They are the only users who can access the API key, manage integrations and team notifications, and cancel the subscription.
Are access roles available on all plans?
Yes. All plans will use the new access roles system, but the level of customization differs by plan.
Starter includes the four default access roles. These roles can't be customized at the role level, but you can continue to grant additional permissions to individuals as needed.
Pro and Enterprise give you full role-level customization, including the ability to:
Edit default roles: Change a permission once and the change applies to everyone assigned to that role.
Create custom roles: Duplicate an existing role or build one from scratch, with up to 10 access roles per account.
Scope access more precisely: Define access based on project teams, project ownership, people someone manages, or selected departments.
Fine-tune access with more granular permissions: Configure viewing and editing independently where applicable.
Do I need to do anything about permission overrides?
No. There's nothing you need to fix on day one. Overrides are there to preserve your team's existing access during migration and for customizing access for individual users. You can leave them in place.
However, as a best practice, we recommend using access roles wherever possible rather than relying on individual overrides in the long term. A role-based access setup is easier to understand and maintain. When several people need the same access, you can manage that access once through their role instead of updating each person individually. There's no deadline to review your setup. You can make changes when it makes sense for your team.
What's the best way to clean up overrides?
Start by looking for people whose access can be represented by one of your available roles.
On Starter, you can assign people to one of the four default access roles. If someone's access should simply match a default role, removing their individual overrides gives you a cleaner setup. You can also keep individual overrides where they're needed.
On Pro and Enterprise, you have more flexibility. If several people have the same non-standard permissions, consider creating a custom access role for that group rather than maintaining the same overrides person by person. For example, if five people are assigned to Resource Manager but all have the same additional permissions, you could create a custom role with those permissions and assign all five people to it.
The goal is to use access roles for repeatable patterns and individual overrides only for genuine exceptions.
Does this change impact the API?
Only if your integration uses the /v3/accounts endpoint and reads the account_type or access fields. Both are being deprecated and replaced by a new access_roles field as part of this update. Once your account migrates, these fields may become stale.
For full details on the changes, timing, and what to update, check the Float developer documentation.
Have more questions?
If you have any questions about the new access roles experience or how the migration will affect your account, contact the Float Support team at support@float.com.