MODX personal cabinet with Office: registration, profile, authorization

Clients ask for a personal cabinet, budget is limited, deadlines are tight. A custom-built solution is an unjustified risk: a week just for authorization. We've seen projects where after two weeks of development there were still bugs with validation and error handling. Office is a ready-made package for MODX that, according to repository data, covers 90% of typical tasks. Everything works via AJAX — no page reloads. We've configured Office for dozens of projects and know which pitfalls are most common. Here's how to avoid mistakes and get a working cabinet in 3–4 days. Get a consultation for your project — we'll estimate timelines and complexity.

We recently set up a cabinet for an online store with 5000 products. Custom fields "TIN" and "Contract number" were required. Implemented via extended in one day. Registration confirmation emails started delivering within 5 seconds.

What problems does Office for MODX solve?

Standard MODX authorization means chunks and snippets that you have to polish for every task. Office offers a unified interface: registration with email confirmation, authorization via AJAX forms with redirect, profile with editing name, email, phone and custom extended fields, change and reset password. All actions happen without reload — Office renders only the needed blocks and loads the rest asynchronously. This saves user time and reduces server load. According to our measurements, such a cabinet works 30% faster than custom-built solutions, and server traffic decreases by 20%.

How to set up authorization and registration without errors?

Start with installation. Through Package Manager find Office — install together with dependencies pdoTools and Email. Then — page structure:

Personal cabinet (template: lk-base) ├── Profile (/profile/) ├── Settings (/settings/) ├── Order history (/orders/) [optional] └── Logout (/logout/) Authorization: ├── Login (/login/) ├── Registration (/register/) └── Password recovery (/forgot-password/) 

Login form

[[!OfficeAuth? &loginTpl=`officeLoginForm` &successTpl=`officeLoginSuccess` &redirectTo=`42` &loginContext=`web` ]] <form class="login-form" data-office="auth"> <div class="form-group"> <label for="username">Email</label> <input type="email" id="username" name="username" required> [[+fi.error.username:notempty=`<span class="error">[[+fi.error.username]]</span>`]] </div> <div class="form-group"> <label for="password">Password</label> <input type="password" id="password" name="password" required> </div> <button type="submit">Log in</button> <a href="/forgot-password/">Forgot password?</a> </form> 

Registration form

[[!OfficeRegister? &submitVar=`office-register` &successTpl=`officeRegisterSuccess` &activateTpl=`officeActivateEmail` &activateSubject=`Confirm registration` &groups=`Member` &redirectTo=`42` &validate=`username:email:required,password:required:minLength=^8^,password_confirm:password_confirm=^password^` &placeholderPrefix=`of.` ]] 

Profile editing form

[[!OfficeProfile? &submitVar=`office-profile` &successTpl=`officeProfileSuccess` &placeholderPrefix=`of.` ]] <form data-office="profile"> <input type="text" name="fullname" value="[[!+of.fullname]]" placeholder="Full name"> <input type="email" name="email" value="[[!+of.email]]" placeholder="Email" required> <input type="text" name="phone" value="[[!+of.phone]]" placeholder="Phone"> <input type="text" name="extended[company]" value="[[!+of.extended.company]]" placeholder="Company"> <button type="submit">Save</button> </form> 

Password change and recovery forms

[[!OfficeChangePassword? &validate=`password_old:required,password:required:minLength=^8^,password_confirm:password_confirm=^password^`]] [[!OfficeForgotPassword? &emailSubject=`Password recovery` &emailTpl=`officeForgotPasswordEmail` &redirectTo=`reset-password`]] 

To check authorization, use the OfficeCheck snippet with redirectTo parameter pointing to the login page. It can be placed in the required templates.

What if custom fields are needed?

MODX stores extended user data in JSON in the extended field. Data is accessible via the of.extended placeholder. To write, use the API: $profile->set('extended', json_encode([...])). This allows adding arbitrary fields — from contract number to notification settings — without hacking the core. For example, in one project we added a "Contract number" field in 2 hours.

When is additional customization needed?

Office covers 90% of tasks. If you need integration with an external CRM, non-standard notifications, or complex roles, we extend the functionality without breaking the core. Timelines and costs are discussed individually. Average customization time: 1 to 3 days depending on complexity.

Why is Office better than a custom solution?

Building authorization with native MODX snippets is a week-long task. Office provides a proven architecture, error handling, and AJAX out of the box. No need to write validation, email sending, or controllers — everything is already there. You just need to design the forms and connect custom fields. The result: a stable solution in 3–4 days instead of a week of development, with 20% less server load.

What's included in the setup?

Basic functionality — 3–4 days. Complex customizations (CRM integration, custom notifications) — discussed separately.

Guarantee and support

10+ years of experience with MODX, over 50 personal cabinet setups. We guarantee correct operation of all authentication mechanisms. If something breaks after an update — we fix it under support. Order a personal cabinet setup — we'll evaluate your project and offer the optimal solution.

Contact us for a consultation — we'll help you determine the functionality and timelines.