Work aids or guides for standard vs. customized Confluence environments?

Question

Hi everyone,

I’m currently learning Confluence and other Atlassian tools to help bridge skill gaps on my résumé and prepare for roles that use these platforms.

Are there any work aids, checklists, guides, or other resources that explain:

* What a user can generally expect from a standard, out-of-the-box Confluence setup

* Which commonly used features typically require administrator configuration or customization

* Which features may depend on Marketplace apps, integrations, or a company’s specific plan

* What may be difficult to practice without access to a company environment or paid sandbox

I understand that every organization may configure Confluence differently, and I have heard that some companies purchase sandbox environments specifically for testing their own workflows and customizations. Because of that, I’m trying to better understand where standard product training ends and employer-specific knowledge begins.

My goal is to set realistic expectations for myself and future employers, while also becoming better equipped to recognize opportunities for improved workflows, additional features, integrations, or customization.

Any advice from experienced Confluence users, administrators, or consultants would be greatly appreciated. Thank you in advance!

Kris Klima _K15t_ · Answer

Hi  @Audry Sterba

OK, so here's my 5 cents :)

Rock the Docs has a lot of user and best practices guides (on Spaces, Permissions and Restrictions, Compliance, etc.

Native Confluence functionality

This would depend on what you're using Confluence for. Compliance docs? Running a soccer team? For me, the limitations mostly happen in the area of advanced content management. I love the WYSIWYG editor and page tree drag and drop organization. But for things like semantic versioning of entire spaces, conditional content, making information public, space synchronization, advanced workflows and approvals, you need an app. Which is fine.

Stock Confluence is perfectly fine, for special use cases... there's an app.

The organization’s subscription plan

This would depend on how many users you have in your company. And whether everyone needs access to Confluence.

The number of seats defines the size of your license. And the license of the apps. If you have 200 users in Confluence, apps are billed for 200 users. You can use the Confluence Guests feature (it does have some limits but works). Or you can use an app to allow non-Confluence users to access Confluence content via password or SSO.

Administrator or space-level configuration

That's really up to your specific needs. I would start with defining who gets to access what, and who can edit or view only. Confluence is for collaboration but there are limits. Check things like public links, anonymous access, space admin rights.

A Marketplace app or integration

Depends on your use case. If Confluence basic features are not enough, you need an app. For example, for compliance reasons, you need a watermarked PDF export of your documentation - properly versioned, auditable, etc. You need an app. Does your approval process requires digital signature for every page? You need an app. A proper LMS learning tool? An app.

App integration is easy, apps come with a trial period, most vendors will work with you on setup etc. What might be an a battle is getting marketplace apps through your company's vendor approval process. Not because they're not secure, but because Legal and Finance don't really get the concept of an app for an app.

An organization-specific process or governance decision

In this realm, it's really YOUR organization specific. How's your org structured, what teams you have, what legislation you must comply with. Do you use SAML SSO identity provider? If so, you need Atlassian Guard. Enforcing 2FA, meeting SOC2 or ISO criteria. There's just too many permutations to offer a specific advice.

Barbara Szczesniak · Answer

@Audry Sterba This article and all of the places it links to may help you out: https://community.atlassian.com/forums/Confluence-User-Group-articles/Confluence-Users-%EF%B8%8F-Start-here-%EF%B8%8F/ba-p/3145018

Audry Sterba · Answer

Thank you, Kris! The point that there is no single “common” setup and that organizations need to balance permissions with collaboration is especially helpful.

I think the distinction I am trying to better understand is how an employee or newer administrator can identify whether a particular workflow or limitation comes from:

* Native Confluence functionality

* The organization’s subscription plan

* Administrator or space-level configuration

* A Marketplace app or integration

* An organization-specific process or governance decision

Does Rock the Docs include guidance for making those distinctions, or is there another framework or resource you would recommend?

My goal is not necessarily to recreate every employer environment, but to become better at recognizing what I am looking at and knowing which questions to ask when entering a new organization.