Access must be tied to the relevant customer/tenant and assigned roles.
Login
Login
Customer login must lead to customer surfaces and must never expose the private owner/admin ingress.
EPTT
One clear entry point to the customer’s EPTT environment.
EPTT keeps product, hardware and deployment decisions connected instead of treating them as separate purchases.
Customer functions remain separate from public marketing content.
Installers and documentation should be delivered through controlled customer channels.
Owner/admin systems remain private and are not linked from the customer site.
ACCESS MODEL
Customer access is more than a login field.
The access model should connect identity, customer, role and relevant resources without exposing owner/admin systems on the public site.
Identity
The user should understand their own access context.
Role
Access is limited to relevant customer and operational surfaces.
Boundary
Owner/admin ingress is not part of the public product site.
01Onboarding
A new customer starts through scope and agreed access, not open registration.
02Recovery
MFA/2FA, recovery and step-up remain security controls to document and verify.
03Customer material
Downloads and documentation can be controlled by customer/role.
04Audit
Relevant access and admin events belong in the final security model.
The customer portal now uses the shared TEA2 identity authority. EPTT routes customers through the controlled login entry and customer-scoped access model.
Existing EPTT customer
Sign in to your EPTT customer portal
With an approved EPTT customer account you can view your own subscriptions, devices, downloads and support requests. Owner and customer access remain separate.
Apply for an EPTT account
This is a real application, not an active login. Your request is recorded in TEA2 for follow-up and a quote.