# Customising the html of lock with universal login

**URL:** <https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215>\
**Category:** Get Help\
**Created:** [March 6, 2019, 4:24pm UTC](https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215 "2019-03-06T16:24:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![simon.tamman](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/simon.tamman/32/12822_2.png) [@simon.tamman](https://community.auth0.com/u/simon.tamman)\
**Post date:** [March 6, 2019, 4:24pm UTC](https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215/1 "2019-03-06T16:24:39Z")

</div>

Is there a simple means of doing this? I am guessing no?  
A stakeholder is asking to add a single link somewhere to the login form and the only way I can see to do this is to move to full customisation. However full customisation results in losing lock and its great styling and features.  
Alternatively I then have to fork lock, add my modifications to it and then do something horrible to inline all the js and css and html into the one editable file I have via the full customisation in auth0.  
Am I just being a silly sausage and missing an easier way around this?

---

<div class="post-metadata">

**Author:** ![prashantT](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/prashantt/32/6002_2.png) [@prashantT](https://community.auth0.com/u/prashantT)\
**Post date:** [March 7, 2019, 1:32am UTC](https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215/3 "2019-03-07T01:32:12Z")

</div>

Lock supports a limited set of customizations that can be applied. If the link is a Terms and Conditions link, one thing you could explore is the `mustAcceptTerms` [configuration option](https://auth0.com/docs/libraries/lock/v11/configuration#mustacceptterms-boolean-) in Lock.

For other requirements that aren’t met by the existing set of customizations, our recommendation is to use a custom UI using [Auth0.js](https://auth0.com/docs/libraries/auth0js/v9).

---

<div class="post-metadata">

**Author:** ![simon.tamman](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/simon.tamman/32/12822_2.png) [@simon.tamman](https://community.auth0.com/u/simon.tamman)\
**Post date:** [March 7, 2019, 10:54am UTC](https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215/4 "2019-03-07T10:54:03Z")

</div>

Thanks for getting back to me hyper-quick and for confirming what I suspected. I get why you do this and to be honest, I agree. If my stakeholders had their way the login screen would be a hideous mess of a requirements pit and this outcome makes my life easier.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [March 7, 2019, 11:13am UTC](https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215/5 "2019-03-07T11:13:49Z")

</div>

Glad you understood our reasoning behind it 🙂 Let us know if you have any other questions regarding custom UI!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 26, 2019, 2:30pm UTC](https://community.auth0.com/t/customising-the-html-of-lock-with-universal-login/22215/7 "2019-03-26T14:30:00Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
