# Terms and Conditions

**URL:** https://community.tago.io/t/terms-and-conditions/1427
**Category:** Analysis and Actions
**Created:** [July 2, 2023, 6:26pm UTC](https://community.tago.io/t/terms-and-conditions/1427 "2023-07-02T18:26:10Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![agriot.info](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@agriot.info](https://community.tago.io/u/agriot.info)
#### Post date: [July 2, 2023, 6:26pm UTC](https://community.tago.io/t/terms-and-conditions/1427/1 "2023-07-02T18:26:10Z")

</div>

Hi

I would like to add a required field on my user login page that requires the user to check a box indicating they have read the terms and conditions before they are allowed to login.

 ![](https://canada1.discourse-cdn.com/flex034/uploads/tagoio1/original/2X/c/c06e09d5291b71ffbf759620497048c2f5fe8913.jpeg)

is this possible?

Thanks

Steven

---

<div class="post-metadata">

### Author: ![mateus.silva](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@mateus.silva](https://community.tago.io/u/mateus.silva)
#### Post date: [July 5, 2023, 2:12pm UTC](https://community.tago.io/t/terms-and-conditions/1427/2 "2023-07-05T14:12:37Z")

</div>

Hi,

Unfortunately, the feature you are currently looking for is not available at the moment. However, we encourage you to submit a feature request for its addition.

To submit a feature request, please visit our designated [Feature Requests](https://help.tago.io/portal/en/community/tagoio/feature-requests) section. By sharing your request, our dedicated team will thoroughly evaluate the feasibility of incorporating this new feature into our system.

---

<div class="post-metadata">

### Author: ![mateus.silva](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@mateus.silva](https://community.tago.io/u/mateus.silva)
#### Post date: [July 12, 2023, 8:07pm UTC](https://community.tago.io/t/terms-and-conditions/1427/3 "2023-07-12T20:07:11Z")

</div>

Hi, Shepherd Technology

There was a mistake on my part, there is a feature that enables a terms and conditions checkbox when creating an account. Follow the steps:

- Go to the ‘RUN’ section  
- Open the tab ‘Signup Page’  
- Scroll to the bottom and add a link under the ‘Terms and Conditions’  
- Attached an example of how this show up in a RUN signup page.

 ![](https://canada1.discourse-cdn.com/flex034/uploads/tagoio1/original/2X/f/faef5a2de73ac6c75c698c9e05d4ccd33aa9f9d6.png)

---

<div class="post-metadata">

### Author: ![agriot.info](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@agriot.info](https://community.tago.io/u/agriot.info)
#### Post date: [August 27, 2023, 2:24pm UTC](https://community.tago.io/t/terms-and-conditions/1427/4 "2023-08-27T14:24:42Z")

</div>

Hi mateus.silva

I did as you suggested a month ago and noticed that when i added a link to our terms and conditions and selected confirmation required a check box appeared at our login page.

We are now ready to roll this out to our customers so that they can accept our terms but it does not work now.

I notice that the check box appears here:

 ![](https://canada1.discourse-cdn.com/flex034/uploads/tagoio1/original/2X/0/034ff95a6af23298a6f28dc3081f4b718bca6baa.png)

But when a user tries to create an account from our tagoio run domain then we get this page with no check box

 ![](https://canada1.discourse-cdn.com/flex034/uploads/tagoio1/original/2X/0/09c83a0a0fea0cb38c8a158ffdf36e7a2b8bc9ce.jpeg)

Then when they click on create account it sends without required t&c’s check box.

 ![](https://canada1.discourse-cdn.com/flex034/uploads/tagoio1/original/2X/f/f6fc885d204244d43d16a992c0d38dd8865cca75.jpeg)

Thanks  
Steven

---

<div class="post-metadata">

### Author: ![mateus.silva](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@mateus.silva](https://community.tago.io/u/mateus.silva)
#### Post date: [August 29, 2023, 1:24pm UTC](https://community.tago.io/t/terms-and-conditions/1427/5 "2023-08-29T13:24:53Z")

</div>

Hi,

A bug has been identified in the mobile application. Our frontend team has been informed, and they are likely to commence an investigation to resolve the issue in the upcoming weeks.

We value reporting of this matter.
