You can export multiple pages or an entire space in several formats, so you have flexible options for sharing, archiving, or migrating content. XML is the standard choice for space exports, capturing the full structure of a space (pages, attachments, and metadata) in a portable file that’s ideal for moving content between Confluence instances or for backups. HTML provides a static, browsable copy of the content, which is great for offline viewing or archiving because it preserves the look and links of pages as a standalone site. PDF offers a portable document format you can print or share, and you can generate a PDF that covers a set of pages or a page tree, depending on the scope you select. Since each format supports exporting more than one page at once or an entire space, all of these options can be used for exporting multiple pages or spaces.

Targeting specific user groups with an Application Link is best done by placing the app link inside a space and granting access to that space to the desired groups or individual users. This leverages Confluence’s permission model, so only people who have space access can see and use the external application connection. It provides granular, scalable control—you can assign or remove users or groups from the space as needs change. Creating an app link per repository doesn’t map to Confluence’s access model and would complicate management. Limiting access to admin users only is overly restrictive and unnecessary when you can precisely define who should access the integration. Relying on a global access token bypasses user-level permissions and is insecure, as it would grant access regardless of who the user is.

Notification routing for app requests hinges on who can manage apps across the whole instance. When a user requests an app or updates that request, the action involves provisioning or governing software across the system, which sits with those who have administrative rights. Because of that, the emails are directed to System Administrators so they can review, approve or reject the request, and perform the installation if allowed. This centralized approach keeps control secure and avoids flooding everyone with requests, since only those with the authority to manage the app catalog need to see and act on it. Non-admin users don’t have permission to install or approve apps, so they aren’t the intended recipients. Project admins operate within a specific project scope and typically don’t handle global app installations, so they wouldn’t receive these notifications either. Sending to all users would be noisy and potentially unsafe.

Confluence runs on the Java Virtual Machine, and the memory it can use is set by the Java heap size in the startup configuration. The default shipped heap is 64 MB, meaning the JVM starts with 64 MB allocated for the heap and cannot grow beyond that unless you change the settings. This is enough only for basic tests; in real deployments you’d typically increase this to a much larger amount based on workload, by adjusting the startup script (such as setenv.sh/Windows equivalent) to set larger -Xms and -Xmx values or JAVA_MIN_MEM and JAVA_MAX_MEM. Other larger memory values you might configure, like 128 MB, 256 MB, or 512 MB, are common production configurations but are not the default.