For IT and security teams
Employee IDs are stopped by HR integration and IGA. External partner IDs sit outside both. Tactna leaves the employee IdP and IGA in place and turns issuing, changing, detecting and deleting external IDs into a system, without adding to IT's workload.
Customers
Problem
Nothing anywhere stops an external partner's ID.
Employees sync with HR and are reviewed by IGA. Distributor and supplier contacts are in neither the HR system nor the IGA ledger. IT issues their IDs per app on request, and IDs nobody asks to stop simply remain.
How it is solved
Requests from the business, handled by hand per app.
Delegate to partner admins. In-policy actions run automatically; only exceptions need approval.
Partner Self-Service ── Self-registration with admin approval→
Waiting to hear who left. A yearly spreadsheet review.
Detect inactivity and auto-lock. Confirm with the partner and remove from every app.
Auto Lifecycle (idle-ID detection) ── Auto-lock and staged deletion→
Bouncing between the IdP, IGA, and every app's console.
IdP for authentication, IGA for employees, Tactna for external. One policy, one record.
Authentication (Auth0 / Cognito) ── Built-in Auth0 / Cognito and SSO→
A day in that job
A distributor contact changes. It used to mean a request from the business and three admin consoles. Now the distributor admin does it in the Portal, and the audit log records it.
IT sees only the exceptions that need approval.
Over the weekend, 12 IDs were auto-locked at 90 days inactive. Partner admins have received the confirmation request. IT checks the count on the dashboard and does nothing.
The stopping is done by the system.
"Who approved this distributor's IDs, when, and when were they deleted?" Search the distributor in the Activity Log and export a CSV. Ten minutes.
No digging through email. No spreadsheets.
Customers
Distributor onboarding went from weeks to immediate. The 30% zombie accounts were wiped out, and user-management work fell 70%.
FAQ
No. Okta or Entra ID keeps authenticating your employees, while Tactna includes its own identity platform (Auth0 or Amazon Cognito) for external partners. Nothing changes in your internal IdP. If you already use Auth0 for external users, the Tactna team migrates the tenant.
Employees: IGA. External partners: Tactna. IGA is strong at top-down request and approval; Tactna at delegation to partners and reviewing unused IDs. Both sets of evidence can go to the audit.
Yes. The manufacturer's access policy decides what is allowed, and partners can only act within it. Every action is logged, and actions needing approval go to IT.
We hold ISO 27001 and ISO 27017. Data is stored in-region, and the audit log is append-only and tamper-proof.
