Two managers working for the same company can open RemoFirst and see completely different information.
One may have access to an entire department, while another sees only a small project team. One can approve time-off requests, while another can review them but cannot make a decision.
This isn’t necessarily an error. RemoFirst uses Teams and role-based permissions to determine what managers can see and do.
The distinction becomes especially important when companies operate across several countries or manage both contractors and regular staff.
Teams Aren’t the Same as Legal Entities
RemoFirst allows companies to organize people into Teams based on departments, regions, projects, or other operational groups.
These Teams operate independently of legal entities.
A company could create separate groups for Engineering, Customer Support, and a temporary contractor project without establishing a separate legal structure for each.
This makes Teams useful for organizing international operations around actual management responsibilities.
However, creating a Team doesn’t automatically give every manager access to it.
The Default Team Can Cause Confusion
When a company starts using RemoFirst, the platform automatically creates a default Team using the company’s name.
Newly added people are assigned to this Team unless they’re reassigned.
The default Team can be renamed, but it cannot be removed.
This is worth checking when someone unexpectedly appears under the wrong group.
The person may simply have remained in the default Team rather than being assigned to the intended department.
Who Can Create a New Team?
Only the Company Admin can create Teams.
The relevant controls are located under Company Settings → Teams → Create New Team.
The administrator enters a Team name and can assign managers with specific responsibilities.
The Company Admin is automatically assigned as Team Admin for newly created Teams.
Other managers can be added during creation or later through the Team’s settings.
A Team Manager cannot simply create an entirely new organizational group because they manage an existing one.
Why One Manager Sees More Than Another
RemoFirst restricts Team Managers to the Teams assigned to them.
Someone managing the Engineering Team shouldn’t automatically see information belonging to Customer Support.
The platform applies these restrictions across relevant sections, rather than merely hiding names in one directory.
This is an important difference between a display filter and an actual permission boundary.
If a person or request is missing, the first thing to check is whether it belongs to the manager’s assigned Team.
Viewing Time Off Doesn’t Mean Approving It
RemoFirst separates time-off permissions into two roles.
PTO Viewer can see time-off activity but cannot approve or reject requests.
PTO Approver can review requests and take the appropriate approval actions.
This can explain why one manager sees an absence request without having the controls needed to approve it.
The solution isn’t necessarily to recreate the request. The company’s administrator may need to review the manager’s assigned role.
What Can a People Manager Do?
The People Manager role provides broader authority over people-related records.
According to RemoFirst’s permissions documentation, it can include managing personal information, agreements, time-off records, and other personnel-related activities.
This is different from a narrowly defined approval role.
A manager who only needs to review absences may not require the broader People Manager permissions.
RemoFirst allows organizations to delegate specific responsibilities without giving everyone the same administrative authority.
Multiple Roles Can Be Assigned
Managers aren’t restricted to a single role.
A person can have more than one permission group when their responsibilities require it.
For example, a manager might need to review time-off requests and approve expense claims for the same Team.
RemoFirst supports assigning those responsibilities separately.
This is more flexible than treating every manager as either a full administrator or a read-only observer.
It also makes permission reviews important when responsibilities change.
Team Manager and Direct Manager Aren’t Identical
RemoFirst also supports assigning a Direct Manager to an individual worker.
That relationship can determine who receives certain notifications or participates in specific review workflows.
Team membership, meanwhile, controls organizational visibility and role-based authority.
These concepts shouldn’t be treated as interchangeable.
A person’s Direct Manager may be relevant to an individual workflow, while Team permissions determine the broader records and actions available to an administrator.
What Happens When Someone Changes Departments?
A worker may need to be reassigned when moving to another project or department.
RemoFirst allows authorized administrators to edit Team assignments.
This matters because the person’s new Team determines which Team Managers can see the relevant records.
If a transfer has occurred but the platform still displays the person under the old group, the Team assignment may need updating.
Changing someone’s reporting relationship outside RemoFirst doesn’t automatically establish that their Team assignment has been changed inside the platform.
Removing a Team Isn’t Always Simple
RemoFirst allows organizations to remove Teams that are no longer needed.
However, the system prevents removal when people or managers remain assigned to the Team.
Those assignments must be moved to another active Team first.
The removal is permanent, so it isn’t merely a temporary hide option.
This is a useful safeguard against leaving people associated with an organizational group that no longer exists.
Why Permissions Should Be Reviewed Regularly
Teams change. Managers move between departments, contractors finish projects, and responsibilities shift.
RemoFirst allows administrators to add managers, change their roles, or remove their Team assignments.
These controls are useful, but they require maintenance.
A manager who previously needed broad access may no longer require it after changing responsibilities.
Likewise, someone taking over a Team may need additional permissions before they can handle outstanding requests.
The Important Distinction
RemoFirst Teams combines two separate controls: organizational membership and permission roles.
Membership determines which group of people a manager can work with. Roles determine which actions the manager can perform.
When a manager cannot find a person, view a document, or approve a request, don’t assume the record is missing. Check the Team assignment and the manager’s permissions first. The information may exist exactly where it should, but outside that manager’s authorized scope.
