Client portal

Give clients visibility into delivery
without exposing internal operations.

A dedicated client portal where clients see project progress, invoices, and tickets — with every internal note, rate card, and SLA detail safely hidden by server-enforced visibility controls.

Start free trial See enterprise overview
Portal capabilities

Everything clients need — nothing they should not see

Live dashboards, invoice history, ticket tracking, and controlled file access — all in a portal that enforces data isolation at the server level.

Project visibility

Clients see task progress, sprint status, and milestone completion on live dashboards.

Invoice history

Full invoice trail with supporting evidence and SLA credit detail, accessible any time.

Ticket tracking

Clients submit and track support tickets with real-time status and response updates.

Document sharing

Attachments and deliverable documents with Client Visible flag appear in the portal.

Data isolation

Internal notes, rate cards, and SLA formulas are never exposed — enforced server-side.

Client team management

Client Admins manage their own employees within the portal without internal access.

Project visibility

Live project progress without exposing internal operations

Clients get a real-time view of delivery status while the delivery team retains full control over what detail surfaces in the portal.

  • Live task status, completion percentages, and sprint progress visible to clients
  • Milestone tracking shows agreed delivery checkpoints and current standing
  • Sprint board read-only view scoped to Client Visible tasks only
  • Epic and user story progress rolled up into a client-friendly summary dashboard
  • Internal tasks, team discussions, and backlog grooming notes remain hidden
  • Clients cannot see agent workload, internal capacity, or sprint planning detail

Client Portal

Nexus Corp · Client view

Live

Platform Rewrite Q1

CON-2024-018 · Bucket-Based

Active
Delivery Progress 42%

Sprint 12

Current

14

Open Tickets

2

SLA Risk

Recent Invoices

Last 30 days

INV-2026-0041

Due Mar 31

$4,136 Pending

INV-2026-0038

Paid Mar 5

$3,890 Paid

Internal notes, rate cards, SLA calculation logic, and team capacity data are never visible here

Invoice transparency

Invoice history that clients can understand and trust

Every invoice in the portal carries the evidence behind it — SLA credit breakdowns, time records, and supporting deliverable detail — so billing questions are answered before they are asked.

  • Full invoice history accessible at any time from the client portal
  • SLA credit line items show breach reference, duration, and contractual deduction
  • Payment status and outstanding balance visible at a glance
  • Supporting time records and deliverable sign-offs linked per invoice
  • Rate card amounts are shown as agreed totals — internal rate structure never exposed
  • Client can download invoice PDFs and supporting evidence for their own records

INV-2026-0041

Nexus Corp · CON-2024-018

Due Mar 31
Period: Mar 1–31, 2026 31.5h billed

Regular hours

28.5h × $120

$3,420.00

After-hours

3h × $180

$540.00

SLA breach credit

TKT-041

−$200.00

Tax (GST 10%)

on $3,760

$376.00
Subtotal (excl. tax) $3,760.00
Total Due $4,136.00
Immutable after issuance Rate-card matched
Ticket portal

Clients submit and track tickets — internal workflow stays private

Clients have a full ticket lifecycle view from submission to resolution, while the internal escalation path, agent notes, and SLA calculation logic remain entirely private.

  • Clients raise tickets directly from the portal with description and attachments
  • Real-time status updates as the internal team progresses the ticket
  • Response thread visible to the client — internal-only notes are filtered server-side
  • SLA countdown timer optionally surfaced to the client per contract configuration
  • Ticket history searchable and filterable by date, status, and job type
  • Clients cannot see agent assignment, internal escalation steps, or team discussion

Ticket Queue

Prioritised by SLA urgency and support level

3 Near Breach

TKT-0041

API timeout on bulk export

Critical

0h 42m left

TKT-0039

Dashboard charts not loading

High

2h 15m left

TKT-0037

Password reset email delayed

Medium

8h 00m left

TKT-0034

Export to CSV missing columns

Low

2d 4h left

Critical and High tickets escalate automatically near SLA threshold Escalation Ready
Visibility controls

Client Visible / Internal Only enforced server-side — not just hidden in the UI

Every record in Effigate carries a visibility flag. The restriction is evaluated before data leaves the server — no URL manipulation, API call, or browser trick can surface an Internal Only record in a client session.

  • Visibility flag applies to tasks, tickets, notes, comments, attachments, and deliverables
  • Flag is evaluated at the API layer before any data is serialised for the portal
  • Delivery team sets the flag at item level for granular, per-record control
  • Default visibility is configurable per project — teams set the safe default once
  • Internal Only flag covers rate card amounts, SLA formulas, and billing condition logic
  • Audit log records every visibility flag change with actor and timestamp

Visibility Controls

Client Visible vs Internal Only policy

Server Enforced

Task

TSK-0142: OAuth provider fix

Internal Only

Note

Rate negotiation context

Internal Only

Task

TSK-0138: API performance work

Client Visible

Comment

Fix deployed to staging

Client Visible

Attachment

contract-amendment-draft.pdf

Internal Only
Client users never access internal notes, rates, or SLA logic internals Visibility Matrix
Client team structure

Client Admins manage their own team within the portal

Client organisations have their own role hierarchy inside the portal. Client Admins provision and manage Client Employee accounts independently — without requiring any action from the internal delivery team.

  • Client Admin role can create, edit, and deactivate Client Employee accounts
  • Client Employees inherit a read-restricted permission set by default
  • Client Admin controls which portal sections each employee can access
  • Multiple clients per contract supported — each scoped to their own data
  • Internal roles, agent profiles, and team capacity are never visible to any client user
  • Client user authentication is isolated from internal team authentication

Role Hierarchy

Tenant and project permissions model

Strict RBAC

Tenant Roles

Owner

Full platform authority

Level 1

Admin

Settings and user governance

Level 2

Manager

Delivery and resource control

Level 3

Member

Assigned work execution

Level 4

Project Roles

Project Owner Project Manager Contributor Reviewer Observer
How the portal operates

From client login to informed stakeholder — a governed visibility flow

The portal gives clients exactly what they need to stay informed while the internal team retains full operational privacy.

  1. 1
    Step 01

    Client logs in

    Client users authenticate into a dedicated portal scoped to their organisation. No internal routes or data are accessible from a client session.

    • Client credentials
    • Tenant isolation
    • Role-scoped access
  2. 2
    Step 02

    Sees live project data

    Project dashboards, sprint progress, and milestone status update in real time. Only Client Visible items appear — Internal Only records are filtered before the response leaves the server.

    • Task progress
    • Sprint status
    • Milestone tracking
  3. 3
    Step 03

    Reviews invoices and tickets

    Clients access their full invoice trail with supporting evidence and manage their open tickets through the ticket portal. SLA credit breakdowns are visible; rate structures are not.

    • Invoice history
    • SLA credits
    • Ticket management
  4. 4
    Step 04

    Internal team stays protected

    Rate cards, internal notes, agent workloads, SLA formulas, and team discussions remain exclusively internal regardless of portal interactions.

    • Rate card isolation
    • Internal notes hidden
    • SLA logic private
Role-based value

Portal clarity for every stakeholder

Account Managers

Share delivery progress and invoice evidence with clients without constructing manual status reports.

Client Admins

Manage your team's portal access independently and see project and billing status at any time.

Client Employees

Track tickets and project progress relevant to your engagement without internal team distraction.

Internal Teams

Operate without modifying workflows — visibility controls protect internal data automatically.
Integration ecosystem

Connect portal events to your communication stack

Push portal activity — ticket updates, invoice events, and delivery milestones — to the channels your client-facing and delivery teams rely on.

Slack

Send client ticket submissions and invoice events to Slack channels for your delivery team.

Notifications

Email

Deliver ticket status updates and invoice notifications directly to client inboxes.

Notifications

Microsoft Teams

Notify account managers when clients raise tickets or invoices reach overdue status.

Notifications
Frequently asked questions

Questions about the Effigate client portal

Clients see live project progress, sprint status, milestone completion, support tickets they have raised, invoice history with supporting evidence, and any files or deliverables marked Client Visible. Everything flagged Internal Only — including rate cards, SLA formulas, internal notes, and team discussions — is never exposed, and the restriction is enforced server-side, not just hidden in the UI.

Every task, ticket, comment, note, attachment, and deliverable carries a visibility flag that is set to either Client Visible or Internal Only. The flag is evaluated on the server before any data is returned to the portal — there is no scenario in which an Internal Only record leaks to a client session regardless of URL manipulation or API calls. Delivery teams toggle the flag at item level, giving them granular control over what each client sees.

Yes. Clients can raise tickets directly from the portal, track their status in real time, and participate in the response thread. They see status transitions, SLA countdown timers (if enabled for client visibility), and resolution notes. Internal escalation notes, agent assignments, and SLA calculation logic are never shown to the client.

Each client organisation has a Client Admin who can create and manage Client Employee accounts without requiring internal-team involvement. Client Employees inherit a read-restricted permission set by default, and the Client Admin controls which portal sections each employee can access. Internal roles, rate information, and agent workloads are never visible to any client user regardless of their portal role.

The client portal is available on Professional and Enterprise plans. The number of concurrent client users and portal-enabled contracts varies by plan tier. All plans enforce the same server-side data isolation guarantees — there is no plan-level setting that disables the Client Visible / Internal Only enforcement.

Get started

Give clients visibility without exposing internal operations

14-day free trial. Full portal capability with server-enforced data isolation from day one.

Start free trial View pricing

Related features

Billing Engine Project Management Reporting & Analytics Permissions & Access Control