External partner management ── for companies issuing IDs to distributors, suppliers, and contractors
Distributors, suppliers, contractors. IDs issued to people outside your company are managed in one lifecycle, from issue through review to deletion. The manufacturer's systems follow joiners, handovers, and leavers automatically.
Customers
Problem
Employee IDs stop with the HR feed. Partner IDs never stop.
One manufacturer, dozens to hundreds of partners, several applications. Partners' joiners, handovers, and leavers never reach the manufacturer's systems, even less so when each app has a different admin.
How it is solved
Form → sign-offs → IT issues per app. Weeks.
The moment a partner admin adds someone, policy issues access to every app.
Partner Self-Service ── An admin per distributor and role policies→
Nobody tells you they left. The account stays open.
Detect inactivity and auto-lock. Confirm with the partner, remove from every app.
Auto Lifecycle (idle-ID detection) ── Auto-lock and staged deletion→
A yearly spreadsheet reconciliation. Rows with no reply just stay.
Always current by last login. Reviews and results kept as evidence.
A day in that job
A new rep joins the distributor's sales office. The admin enters an email and the role "Sales" in the portal. Ordering and price-list accounts are issued on the spot; by afternoon on day one they are entering orders.
No form. For the manufacturer's IT, just one line in the audit log.
A supplier's quality contact changes. Their admin removes the old one and adds the new. Access is granted only to the quality-documents app; drawings and pricing stay hidden.
Procurement forwards no email. The old contact's ID is revoked from every app the moment it is deleted.
The IDs of 40 contractor workers are auto-locked once the site's end date passes. The foreman gets a confirmation request and re-enables only the 12 moving to the next site. The rest are deleted after 30 days.
The contractor's IT no longer worries who can still see drawings after handover.
Customers
Distributor onboarding went from weeks to immediate. The 30% zombie accounts were wiped out, and user-management work fell 70%.
FAQ
Yes. The Tactna Portal used by partner admins only asks for an email and a role. No IT knowledge needed. You can also route only approval-required actions to the manufacturer.
No. The identity platform (Auth0 or Amazon Cognito) is provided inside Tactna, and each app simply connects to Tactna with SAML / OIDC. Users and roles are synchronized from Tactna, so apps carry no user management of their own. The Tactna team migrates your existing users.
Yes, in bulk from CSV. Export the user list from your existing apps and import it mapped to teams and roles. Tactna's specialist team helps with the design as part of onboarding.
Yes. The inactivity threshold is 30 to 365 days and can be set per app or team. Who confirms after a lock and the grace period before deletion are configurable too.
