OliverH | Posts: 28

Shared Layout

0 votes
Hey team, In our workflow, we use Designer to design and create package and save documents as layouts. My question is, can you explain more about what "share layout" button does and do you have a separate page to show all layouts I created? Thanks!

Duo_Liang | Posts: 3776

Reply to: Shared Layout

0 votes
Hi Olive, Both TEMPLATE and LAYOUT are package types and also, they have the similar concept "Shared", this is an attribute in your pakcage JSON:"visibility". If you set Visibility.SENDER to your layout/template, it means the template is only accessible to the sender of the package. If you wish to share your layout/template with your other senders, you will need to change the visibility to Visibility.ACCOUNT. You can find the whole JSON schema of a package in this REST quickstart guide. Hope this could help! Duo

tlolkus | Posts: 20

Reply to: Shared Layout

0 votes

We are an on Prem installation and I was wondering if there is a way in the Back Office to set Visibility=SENDER for all packages we are creating through our integration.  I believe there is a way to do this in code using .withVisibility(Visibility.SENDER) but it would be nice to disable via the Back Office.  If that is available can you let me know what Resource I can update (Feature or Package I would assume) and what the JSON looks like?  We would like to hide the Sharing Layouts feature.  


Duo_Liang | Posts: 3776

Reply to: Shared Layout

0 votes

Hi Tricia,

 

From API/integration's perspective, I believe the only way to define a layout/template as "Not Shared" is to explicitly set visibility as "Sender". Currently there's no related settings in backoffice to override the default visibility (if you didn't specify, the default value is Visibility.ACCOUNT)

 

From UI user's perspective, if you later upgraded to a version which introduced the "Enterprise Administration" function and enabled the "Roles & Permission" feature, the default Regular, Manager, Owner user types will be replaced by a role-permission based system, where "Share Templates" and "Share Layouts" are two available permissions. However, this only removes the option from UI, behind the scene, the API still explicitly set the visibility as Sender.

 

Duo


cdean | Posts: 18

Reply to:

0 votes

Hi Duo Liang,

I have added .WithVisibility(Visibility.SENDER) when we create a package in the hopes of hiding the Shared Layouts UI control.
However, this single code change does not have the desired affect of hiding this control in the UI.
Do we need to do anything further in the code to achieve this?


Duo_Liang | Posts: 3776

Reply to:

0 votes

Hi Clayton,

 

Yes, this code change could effectively limit the visibility to the sender him/herself for all layouts created by integration, in which case if all layouts are created from integration, whether toggled on the "Show Shared" button return the same result.

However as you observed, package level setting won't affect the account level UI preference. If you also want to hide the "Show Shared" button when applying the layout in designer (below screenshot is made in classic sender UI portal). Unfortunately, it's not customizable for your on-premise version. 

As I explained above, in a foreseeable future upgrade, to show/hide "Show Shared" becomes a role's permission and allows the admin user to specify per-sender basis.

10-29-1

 

Duo


cdean | Posts: 18

Reply to: Shared Layout

0 votes

Thank you, Duo


I have a newbie question, what is meant by

"could effectively limit the visibility to the sender him/herself for all layouts created by integration"


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off