Request a demo
Menu

Fctr Portal

Verify the caller. Proceed with approved actions.

Verify employees with existing factors, review live user details, and resolve support requests in one helpdesk workspace.

Fctr PortalHelpdesk workspace
Maya ChenLive directory
MC
Maya ChenActive employee · Finance
Microsoft Entra ID
Groups
Finance · Employees
Personal contacts
Masked for the agent
01 / Identity verificationCaller verified.Existing enrolled factor confirmed
02 / Role + target policyAction permitted
Password reset

Identity verified. Permission checked separately.

Fctr Portal workspace showing live directory context, masked personal contacts, enrolled-factor verification, and a separate role and policy check for a password reset.
Request a demo Explore the workspace
Built for
Entra ID
Okta

One console for the whole support call.

  1. 01

    Find the user

    Search your live directory and inspect the employee's profile, groups, and devices.

  2. 02

    Verify the caller

    Use a supported enrolled factor or an approved alternative required by your policy.

  3. 03

    Take the allowed action

    Apply the agent's role, target restrictions, and action policy before proceeding.

  4. 04

    Keep connected evidence

    Review the verification, authorization, and outcome in PII-masked audit history.

Review the control model

The context agents need.
The privacy people expect.

Keep profile details, group membership, devices, and sign-in activity in the same workspace. Supported Entra ID workflows also expose license context.

Personal phone numbers and email addresses are masked for agents according to role. Fctr retrieves live context for active support work rather than maintaining a shadow directory.

Directory context

Entra ID / Okta
MC
Maya ChenFinance · Employee
Active
Identity
Profile and account state
Access
Groups and applications
Devices
Registered device context
Activity
Sign-in information
Privacy
Role-based PII masking

Give agents the tools.
Keep access in scope.

Let your helpdesk resolve supported requests without giving every agent broad access to provider admin consoles. Caller verification precedes resets and supported unlocks; roles and policy determine what follows.

  • Scoped roles. Decide which support actions each agent can perform.
  • Protected accounts. Configure exclusions by supported role, group, or identifier pattern to keep matching accounts out of lookup and selection.
  • Verification that fits the request. Use supported enrolled factors, or Entra Verified ID with Face Check for supported employee workflows where configured.
How verification fits an unlock workflow
01 · Verify the caller

Identity verification

Supported factor confirmed

02 · Check permissions

Role + action policy

Agent, target, and action permitted

Approved support action
Identity verification and role and action policy checks precede an approved support action.

More than
password resets.

Resolve identity support requests through the same governed workflow. Available actions depend on your provider, setup, and policy.

01

Account recovery

Reset passwords, unlock supported Okta accounts, and enable supported Entra ID accounts after required verification and policy checks.

02

Session and temporary access

Revoke sessions and issue supported Entra ID Temporary Access Passes or Okta Temporary Access Codes where enabled.

03

Authentication methods

Update or remove supported authentication methods after verification, agent-role checks, and the applicable policy requirements.

04

Audit review

Search support history and export records that connect caller verification, authorization, and the action outcome.

Every support action.
Recorded and auditable.

Record who performed each support action, the verification and policy checks, and the outcome in PII-masked audit history.

Authorized administrators can search support history and export records for operations and security reviews. Personal and recovery contact details stay out of approved audit records.

Explore the security model
Support historyAdmin view
MC
Password resetMaya Chen · Employee
Completed
Actor
Helpdesk agent
Verification
Enrolled factor confirmed
Authorization
Role + target policy checked
Action
Password reset
Outcome
Completed
Record
PII-masked audit evidence
Search and export for authorized administrators
Support audit record connecting the agent, verification, authorization, password-reset action, and outcome in the administrator view.

Entra ID or Okta.
One familiar workspace.

Your identity platform can change. Your helpdesk workspace doesn't have to. Keep user context, verification, and approved actions together for in-house or outsourced support teams.

Microsoft Entra ID
Okta

Fctr Verify

Let employees
verify the caller.

Fctr Verify covers the other side of the conversation and colleague requests, with employee access through configured Teams or Outlook apps. Fctr Mobile adds a standalone path in private beta, available by invitation.

Explore Fctr Verify

Per helpdesk agent.
Not per employee.

Start with a tailored demo, then scope a pilot around your support tasks and environment.

Request a Portal demo

No customer tenant access needed for the demo.

Fctr Portal

$250per agent / month

10-agent minimum · Billed annually

  • One helpdesk workspace
  • Existing-factor verification
  • Role-governed support actions
  • Connected, PII-masked evidence

Add Fctr Verify and supported integrations at discounted bundle pricing. Request a combined quote.

View all pricing options

Questions about
the workspace.

For your security review

Trust Center Security model DPA
What is Fctr Portal?

Fctr Portal is helpdesk identity verification and account recovery software. Agents can find users, review live Microsoft Entra ID or Okta details, verify callers, and perform approved support actions without switching between separate admin consoles. Verification, authorization, and the outcome stay connected in PII-masked audit history.

Can we use our existing verification methods?

Yes. Fctr Portal uses supported factors your organization manages in Entra ID or Okta. Entra Verified ID + Face Check is an additional option for supported workflows where configured. We can show you the choices that fit your provider and policies.

Can we use manager verification?

Where configured, manager verification is an approved alternative. Fctr verifies the manager with enrolled factors. Your support policy determines how the employee's identity is confirmed and which actions are permitted.

Do helpdesk agents need standing Entra ID or Okta administrator roles?

For supported workflows, Fctr Portal lets agents perform approved actions without assigning them the corresponding standing Entra ID or Okta administrator roles. Agents still need permission in Fctr; provider-role requirements depend on the action and identity setup.

Is verification required before password resets or account unlocks?

Yes. Password resets and supported Okta account unlocks require valid workflow verification before the action is allowed. Fctr separately checks the agent's role, account restrictions, and policy.

Can we exclude privileged or sensitive accounts?

Yes. Configure exclusions using supported provider roles, groups, or identifier patterns. Matching accounts stay out of Portal lookup and selection, so agents cannot choose them for a reset.

Do we need both Portal and Verify?

No. Portal is the helpdesk workspace. Verify brings identity verification into existing tools through supported customer-deployed integrations. Choose either or combine them. Portal customers receive discounted bundle pricing for Fctr Verify and supported integrations.

Is Portal priced per employee?

No. Fctr Portal is $250 per helpdesk agent per month, billed annually with a 10-agent minimum ($30,000 per year). Larger helpdesk teams can request custom Enterprise pricing. Standalone Fctr Verify uses separate annual pricing. Compare the options.

Bring control to
the next support call.

See live identity context, caller verification, and governed actions working together.

Request a demo