Skip to main content
Solved

Sharing custom shape library within company

  • 4 September 2024
  • 4 replies
  • 44 views

I recently created a custom shapes library using the external API and would like to share it internally with my coworkers.  Based on https://lucid.readme.io/docs/publishing, it looks like “Private Publishing” is the way to go.

There are a couple of snags:

  1. I am not an administrator on this account
  2. A marketplace listing is required, which in turn asks for URLs for a privacy policy and terms of service.  This shapes library has neither, and I don’t think I have access to hosting for this purpose.  (perhaps I could use https://example.com/ ?)

Suppose I create the marketplace listing and reach out to an account administrator and they are willing to help publish this shapes library.  It looks like I would have to add them as an application owner for the library under Collaborators → Invite in the developer portal.  All they would have to do at that point is click publish, select the version, and select “publish privately”, right?

 

Are there other ways to share custom shape libraries internally? @jkrueger hinted that there might be a more convenient way.  The method at https://help.lucid.co/hc/en-us/articles/14931750819476-Shape-libraries-in-Lucidchart#how-to-share-a-custom-shape-library  does not seem to apply to custom shape libraries created with the external API.

I created a marketplace listing and found what is either a bug or just confusing instructions.

On the edit listing page, there is a Support URL / Email field.

If I type user@example.com, it accepts this.  But when I open the listing, there’s a third link titled “Support” which points to https://example.com, omitting the email username entirely.

When I go to edit the listing again, I now find https://user@example.com in the field.

The field does not accept mailto: syntax.

Perhaps this hasn’t been exercised before because these listings are more geared toward bigger users / entire companies.

Hi Ben,

We recommend publishing the app privately to your account. You're correct about the process—it involves inviting an account admin to your app so they can handle the private publishing.

Regarding the Support URL/Email field, we agree that the current behavior isn't ideal. We'll look into this issue further and keep you updated. Thanks for bringing it to our attention!

Ben - the evaluation was quick… we’re going to make it so the Support URL accepts mailto. My guess is it will take us a few business days to get the change live.

Thanks for building on our API! Feel free to let us know if you have other feedback/questions/friction.

Hi Ben,

The Support URL/Email field in marketplace listings now supports `mailto:` email addresses.

You can either choose to specify the `mailto:` protocol or just provide an email address. If only an email address is specified, then `mailto:` will be prepended automatically so the behavior is the same in either case.

Thanks for helping us improve our private-publishing process!

Reply


Lucid Software Inc. Supplemental Community Terms