General
| Expand | ||
|---|---|---|
| ||
...
| Expand | ||
|---|---|---|
| ||
You can choose to data residency in either the US or in the EU. |
| Expand | ||
|---|---|---|
| ||
Read a detailed feature comparison in our migration documentation: |
Pricing and licensing
| Expand | ||
|---|---|---|
| ||
Use the Atlassian license cost calculator. Please note that apps are based on number of users and not agents, which means that for a JSM setup the price might vary. |
...
Refined Sites for Confluence
| Expand | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
| Info |
| Note |
|---|
To show and edit pages exactly as in native Confluence, enable embedded Confluence pages. |
On Refined Sites for Confluence Cloud, permissions can’t be added to a site or page (called categories on Server) level. However you can add view permissions to the content sections on a page. On Refined Sites for Confluence Server/DC it is possible to add view permissions on a category level. Both apps by default will respect the permissions set up in Confluence on spaces and pages.
When editing a Confluence page in Refined Sites for Confluence Cloud the editor will open in a new tab, opening Confluence itself. Changes will take effect as you would expect on the Refined page. On Refined Sites for Confluence Server editing a Confluence page will open up the editor in the same window.
On Cloud, you edit your pages in the what-you-see-is-what-you-get Page Builder (instead of the Layout Editor which you use on Server/DC).
| title | How does I edit a Confluence page on a Refined site? |
|---|
Refined Sites refers you to edit the page in Confluence in a new tab. Whenever you make changes in Confluence, they are immediately visible on your Refined site too.
| Expand | ||
|---|---|---|
| ||
Refined sites show pages, spaces and Confluence pages based on the visitor’s user’s Confluence permissions. You can add additional permissions to your sites and (sections of) pages. |
| Expand | ||
|---|---|---|
| ||
Although Refined Sites doesn’t include a versioning functionality, it’s easy to use Confluence permissions to control what end users see. Because Refined Sites respects Confluence permissions, your sites only show content (pages or blog posts) that the user is allowed to see in native Confluence. When editors work on new Confluence content, restrict the content’s permissions so it’s only visible to them. Once the content is ready, change the permissions to make it available to all end users. Alternatively, you can use Comala Publishing (or another versioning app in Confluence) to only show published content on a Refined site. Just make sure to add the target spaces from your Comala Publishing setup to the site (and not the source spaces). Your Refined sites always show the last published versions of content in those spaces and respect the content’s Confluence permissions. Read how the app works in Comala Publishing’s documentation. |
...
| Expand | ||
|---|---|---|
| ||
Customers who created their account after 20 August 2023 Due to maintenance, it’s temporarily not possible youto add Jira projects to Refined sites. You can only add JSM projects to Refined sites. If you have questions about this, please contact us. Customers who created their account before 20 August 2023 If you already have both Atlassian Jira and Jira Service Management, you only need to purchase one app: Refined Sites for Jira Service Management. |
...
| Expand | ||
|---|---|---|
| ||
In default JSM, it is possible for anonymous users to see a portal and file a ticket without creating an account. This is currently not possible using Refined Sites for Jira Service Management Cloud. We can’t develop this option, because there are no APIs from Atlassian supporting this. |
...