Force accept company policies
Asked by Fernando Morales:

Hello,

is there a posibility to force a User to accept special company policies before using confluence? Something like the What's new Pop-up, but without the close-option.

thx

Fernando


Answers:
author: JamieA
body: Update: I've written a simple plugin to display terms and conditions when an editor is invoked, as in my use case I only need contributors to accept Ts and Cs. This is better than the solution below, as you can't continue editing without accepting, and it doesn't waste screen real estate. Walking the floors I noticed that many people never bothered accepting.

![](https://studio.plugins.atlassian.com/wiki/download/attachments/2261359/Capture.PNG)

You will need to edit the Ts \& Cs text, then deploy. Code here: <https://bitbucket.org/jamieechlin/confluence-ts-and-cs-plugin>. It will require maven to build.

Older solution below:

We use the following code in the announcement banner, which makes people acknowledge Ts\&Cs every 30 days. You could change the 30 to 30000 if you wanted it to be a one-off. It's a bit hacky but has kept various compliance depts of my back. You need jquery.cookie.js which you can find on the interwebs.

```
&lt;script type="text/javascript" language="javascript" src="/confluence/includes/js/jquery.cookie.js"&gt;&lt;/script&gt;&lt;div id="idiotBanner" style="display:none"&gt;    &lt;table style="width: 100%;border: 2px solid #FF0000" cellpadding="2"&gt;        &lt;tr&gt;            &lt;td&gt;                &lt;h3 style="text-align:center"&gt;Important Information &lt;/h3&gt;                &lt;p style="text-align:center"&gt;Because unrestricted wiki pages are visible to all **** users, please make                    sure that all pages/spaces are                    &lt;a href="http://****/Confluence+Acceptable+Usage+and+how+to+permission+pages+appropriately"&gt;                        restricted to appropriate user groups&lt;/a&gt;. Access to sensitive information (e.g.                    login credentials, privileged information) should be strictly controlled and                    those pages restricted to blah blah blah.                &lt;/p&gt;                &lt;p style="text-align:center"&gt;&lt;a href="#" onclick="hideIdiotBanner()"&gt;Acknowledge and dismiss&lt;/a&gt;&lt;/p&gt;            &lt;/td&gt;        &lt;/tr&gt;    &lt;/table&gt;&lt;/div&gt;&lt;script type="text/javascript" language="javascript"&gt;    jQuery(document).ready(function() {        if (jQuery.cookie('hideIdiotBanner') != 'true') {            jQuery('#idiotBanner').show();        }    });    function hideIdiotBanner() {        jQuery.cookie("hideIdiotBanner", "true", { expires: 30, path: '/confluence' });        jQuery('#idiotBanner').hide();    }&lt;/script&gt;
```

comments: author: Dieter
body: Vote up for the cookie name :)


author: JamieA
body: If I told you the story of why I had to do this, you'd be surprised I hadn't thought up a much worse name ;-)


author: Joe Clark
body: Don't forget to tell your users about the behaviour and contents of your cookie storage if you want to avoid prosecution in the EU! :-p


author: JamieA
body: It's not accessible to the public but good point! \<searches for the Atlassian policy on same ;-) \>