Can we remove a site from Guard subscription?

[hydravaronis]

Hello team,

For a Guard subscription, is it possible to selectively include or exclude specific Confluence sites within the subscription scope? My understanding is that Guard operates at the organisation level and billing is user-based, but I’d like to confirm if any site-level control is supported.

Additionally, from an audit logging perspective, does the Confluence site tier (Free, Standard, or Premium) have any impact when Guard is enabled? Specifically, are there any differences in audit log availability, depth, or features based on the site plan in conjunction with a Guard licence?

[Arkadiusz Wroblewski]

Hello @hydravaronis 

Just a quick clarification to @Derek Fields _RightStar_  answer,

Guard is billed at the organization level per unique active user. It cannot be enabled or removed for individual Confluence sites.

Confluence Free lacks native logs entirely. Guard Standard only provides organization-level security logs. To get Confluence product admin logs, you need Confluence Premium (with Guard Standard); for full Confluence user activity logs, you need Guard Premium.

Still it's not really clear to me, what exactly you wanna achieve?

Best,

Arkadiusz 🤠 ☀️ 

[Derek Fields _RightStar_]

It isn't clear what you are trying to do. If your concern is that you want to allow users of one Confluence site to utilize SSO through Guard, but not users in another site, you would accomplish this by putting the users of the second site into a different Authentication policy. You aren't removing the Confluence site so much as you are indicating which users are going to be associated with SSO and therefore with Guard. 

Auditing isn't affected by the Confluence plan. It is affected by the Guard plan. Guard Premium provides data-level protections that will be logged along with other events that Guard Standard doesn't support.

Does this help?