For developers
Your support team can’t use TrustedLogin until someone embeds the SDK. This page is the shortest route from here to a working Grant Support Access button inside your product.
Who this is for
The developer at a plugin or theme company who has been handed the integration, and wants to read the code before shipping it to customer sites.
If you’re deciding whether to buy rather than how to build, the vendors page makes that case instead. Nothing here is for the customer granting access.
Three components
SDK — trustedlogin/client
A Composer package, GPLv2 and open source. It ships inside your plugin or theme and draws the Grant Support Access control in your own admin UI. On a grant it creates the scoped WordPress account on the customer’s site and encrypts the login secret before anything leaves their server.
SaaS — app.trustedlogin.com
The hosted service. It relays and stores the encrypted grant, routes it to your team, and keeps the audit log across every site that has granted you access. It never holds the key that opens what it carries.
Connector — WordPress plugin
Installed on your own site, not the customer’s. It holds the private key that decrypts a grant, connects grants to your support desk, and carries one-time secrets. GPL-licensed, shipped through WordPress.org.
What integrating takes
Add the SDK with Composer, namespace it with Strauss or PHP-Scoper so it can’t collide with another plugin shipping the same code, namespace the CSS, load the namespaced autoloader, write the configuration array that sets the role and duration you’ll request, and instantiate the client on plugins_loaded. The installation guide walks each step with the code.
There’s a second path. The docs ship an AI Integration Prompt written to be pasted into a coding assistant. It covers the same steps plus conflict detection for a plugin that already has its own composer.json, and it reads as the thorough checklist if you’d rather work through it by hand.
The role and duration are yours, set once in configuration. The customer sees what you configured and grants it or doesn’t; there is no per-grant picker for them to get wrong.
Read the source before you ship it
Client SDK docs
Architecture
You need an account before the SDK has anything to talk to. The free plan covers one customer site and five support logins a month, which is enough to build the integration and test it.