Hello guys! Can I hide my templates and workflows for my clients? They are signed in as a Organization and me as a App dev. I want to make my templates are secure and not a subject for duplication.
Thanks in advance // David.
Hi David,
If your client is the owner organization and you are building in their organization as App Developer, you are building scenario’s in their account. So they have full control, you are not able to hide scenario’s.
Only the Teams and Enterprise plan gives you more granular control with Team access for certain users, but then again only if you own the organization, you can manage this: Teams - Help Center
Cheers,
Henk
Appreciate the quick reply!
I saw that someone else wrote this:
“As for the Make “source code” — it’s like anything other intellectual property. We license our scenarios and our customers sign a contract that they won’t modify or resell the scenarios. The scenarios only run with a license, but someone could remove that quite easily and neuter our scenarios so they can run for free.
In effect Make scenarios are open source in their very nature. That’s why the only way to monetize is through support and future services/enhancements of the scenario. If someone wants to steal your stuff they will and you’ll have to go after them.”
This seems problematic, so we’re trying to figure out the best solution here, and looking through your pro’s vs con’s list the most secure and lucrative option seems to be having everything on my own account and using a teams plan:
In the con’s list of this approach you mentioned this “Client must be willing to share credentials for each connection.”
And this is something we noticed, as we attempted to set-up a project by sharing the Make A Connection link for the email module to the client, where he is supposed to log in to authenticate, but the client received this error: “detail”:“Access denied.”,“message”:“User is not logged in.”,“code”:“IM015”,“suberrors”:[]}
So I’m thinking another option is using Zoom and let the client hi-jack our screenshare so that he can enter his password live, that should be a great workaround no?
Can you shed some light given our situation? What would you recommend here?
//David
There’s no single best approach, it really depends on your agreement with the customer. You can sell scenarios for their own use and offer additional services, or retain IP while deploying in their account. However, you then can’t fully prevent or easily prove misuse.
For customer-managed accounts, does it matter? We don’t spend our time building constraints or additional licensing, our customers are free to build and edit whatever they please and we offer them additional services. Our customers reselling scenario’s doesn’t make sense, they are tailored to their needs.
Don’t overestimate how easily scenario’s are sold, the ones that are actually bring value are not templatized easily.
For managed accounts, you’ll need customer credentials for third-party services. The connection link won’t work due to authentication flow restrictions, so you’ll have to find a way to get acces to the services. Can be done anyway you prefer.
My recommendation: Start with clear contracts about IP ownership and usage rights. Most successful automation partnerships are built on trust rather than technical restrictions.
Cheers,
Henk
1 Like