I have a large (personal) study resource which I’ve created in Coda and I’m looking at ways in which I can monetise access for other people in the future. The idea is that people would be invited to the study resource workspace with limited access controls such that they could view content and make minor changes or add comments.
Is it against the Coda terms and conditions to charge people for access to be doc editors in this circumstance?
Hi Andrew, there is nothing preventing you to do that. Unfortunately, there is no mechanism available from Coda to charge for a doc, only for a pack.
You have three options that I am aware of
The one thing to be aware of is the Coda branding. Make sure that you keep that in mind
I think he means keeping the doc in his Workspace and adding people manually as editors who subscribe in some other way.
Yes, correct. I’d like to be able to iterate on both the design as well as the content and I’d like people to be able to collaborate (in some limited form, even if it’s only commenting on different elements).
I could create a pack for the data but that means people are stuck with whatever original doc they copied. It also means there would be no way for people to collaborate on the content.
I could create an embed somewhere inside a walled garden, but it would not be difficult to reverse engineer the link as Coda has no domain restriction tools as far as I’m aware.
The only option I can really think of is to either manually, or via some automated mechanism with Enterprise API, invite people to the workspace on a subscription basis.
Edited to add: the issue I see is that I could, theoretically, ask people to subscribe and then create a personal doc for each of them to edit at will. If I charge a lower price than a regular Coda subscription then I am basically offering them a subset of Coda features at a cheaper price than Coda. Sounds like something that would be viewed dimly.
As long as they’re not makers, you’re good. In other words, as long as they don’t create pages.
Giving many people access to a single doc in your workspace has the downside that they all can see all of the doc.
If you are sharing information, that is ok. If the customer needs to be able to capture information, it becomes less ok.
If you want to share functionality, while retaining the ability to upgrade the functionality it becomes a whole different kettle of fish.
What I am looking at is containing the functionality in a set of sync pages. As soon as you update a sync page in the source doc, the destination doc is updated as well. Which could be an advantage or a disadvantage.