TempLoginAuthentication
The alpha uses email possession and a one-time link. Authenticator-based MFA, enrolment and recovery are future implementation. A second message to the same inbox will not be called independent 2FA.
TEMPORARY WORDPRESS ACCESS, EXPLAINED
The right access.
For the work ahead.
From the first invitation to the last session, TempLogin is being built around a clear relationship between the person, their permissions and their approved time.
See current alpha scope ↗Product direction · Individual features below distinguish alpha implementation from future development.
01 / INVITATIONS
Start with a person.
Keep the scope explicit.
The owner starts every first-time engagement. An email address identifies the invitee; the approved grant sets the permissions and end time. Existing permanent accounts are kept separate.
- Alpha: dedicated identities, Contributor/Author scopes and work windows from one hour to seven days.
- Alpha: 15-minute single-use confirmation links; fresh links do not change the approved end time.
- Future: Editor and administrator workflows, custom permission templates and project/vendor records.
02 / VISIBILITY & CONTROL
An arrival alert.
A useful record of the work.
See when a temporary person signs in and review supported access and content events. Pause or close the grant when the engagement changes.
- Alpha: login notifications, connected IP/browser records, pause/resume/revoke/block and session termination.
- Alpha: core post creation/update/deletion and media additions, local 90-day retention and CSV export.
- Future: integration-specific events, configurable retention, richer reports and externally retained evidence.
03 / RENEWAL
A clear end.
An approved next step.
Previously approved collaborators may have work left to do. Verification and a real grant history come before a renewal request. Pending requests never create permissions.
- Alpha: a fresh owner-issued link lets a paused/expired collaborator ask for more time; the owner approves or denies.
- Alpha: blocked or revoked grants cannot renew. Resume cannot silently revive an expired window.
- Future: self-service recovery for eligible former collaborators, scheduled bans and more approval routes.
SECURITY & GOVERNANCE
Build the foundation.
Then widen the policy.
Login safety belongs in the free core. Paid value comes from coordination, scale and organisation policy.
Team decisions
Business will add permission templates, vendor records, approval routing, maintenance windows and detailed reports. These are proposed features, not alpha capabilities.
Reviewable governance
Enterprise will add mandatory policies, independent approvals, access reviews and external evidence. These can support security processes; they do not certify a site or an organisation.
A free foundation.
Room for your team.
Review the proposed editions and tell us what your handovers need.