# Feature NEX-327 - Disable TOS(term_of_service) for user OpenProject when app is enabled

Project: Stream Nextcloud app "OpenProject Integration"
Status: closed
URL: https://community.openproject.org/work_packages/NEX-327

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Nextcloud Integration 2.6.1 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Sagar Gurung |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

We have a special user `OpenProject`  which is created when we set up the project folders. when app TOS (term\_of\_service) is enabled all the user has to accept the term of service but user `OpenProject` never logs in to accept the TOS.

TODO:

*   Detect the TOS and disbale the TOS for the user `OpenProject`

**Some information and findings to solve this issue:**

The initial solution for disabling the TOS for the OpenProject was to set a limit to a group if it was possible but the for `TOS`  we cannot set it limit to groups.

So possible solution after some findings are:

1.  To sign `TOS` for user `OpenProject` when the app is enabled (After the project folder set up is already done)
2.  To sign `TOS` for user `OpenProject`  when setting up project folder ( `terms_of_service` app is already enabled)
3.  To sign `TOS` for user `OpenProject` (if available) when creating new `TOS` by admin.

The first 2 points can be achieved but for the 3rd one when `terms_of_service` app is enabled without any `TOS` and project folder is also setup already setup. When the admin creates new `TOS` then we might have to sign that `TOS` for user `OpenProject` which is so far not possible to do so.

But, the possible solution for the 3rd points could be:

1.  setting up a new `TOS` created Event so that it can be Listened and we can sign TOS for user `OpenProject` through that listener.
2.  implement in `terms_of_service` app to exclude to sign `TOS` for users. (OpenProject user in our case)

  

**Note:** Solution is TBD in meeting.