Skip to Content
Last modified by Alex Cotiuga on 2026/07/13 06:44
From version 6.2
edited by Alex Cotiuga
on 2026/07/13 06:44
Change comment: There is no comment for this version
To version 5.2
edited by Alex Cotiuga
on 2026/07/03 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -138,7 +138,6 @@
138 138   areas that need a cleaner governance model.
139 139   </p>
140 140   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an access review</a>
141 - <a class="btn btn-secondary" href="$xwiki.getURL('pricing.WebHome')#common-packages">View review pricing</a>
142 142   </div>
143 143  
144 144   <h2 id="governance-model">A safer model for XWiki access rights</h2>
... ... @@ -266,6 +266,17 @@
266 266   <a href="$xwiki.getURL('resources.xwiki-custom-development')">how to keep XWiki custom development maintainable across upgrades</a>.
267 267   </p>
268 268   </div>
268 +
269 + <div class="resource-cta">
270 + <h3>Need help reviewing XWiki access rights?</h3>
271 + <p>
272 + If your XWiki instance has grown over time, includes restricted areas, uses many groups or depends on
273 + authentication integrations, an access-rights review can help clarify who can access what and where the
274 + permission model should be simplified.
275 + </p>
276 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an access-rights review</a>
277 + </div>
278 +
269 269   </article>
270 270   </div>
271 271   </div>
... ... @@ -280,7 +280,7 @@
280 280   authentication integrations, an access-rights review can help clarify who can access what and where the
281 281   permission model should be simplified.
282 282   </p>
283 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an access-rights review</a>
293 + a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an access-rights review</a>
284 284   </div>
285 285   </div>
286 286   </section>