On the clients subpage there’s a button that makes a copy of the client portal template
Clients suppage has a button to copy the Client Portal template, creating a unique portal for each client (e.g., “Client Portal Oceana”).
Questions:
Client Visibility: Does this setup (Agency Page > Clients Sup > Client Portal Template) ensure each client (e.g., Oceana) only sees their own portal? And not other pages
Project Management: Should project items (proposals, invoices, background, overviews) be created as subpages of the “Client Portal (Template)” for each client?
Agency Tracking: How can the agency owner efficiently track all client communication, projects, tasks, etc. (without switching portals)? (High-level view or specific suppage structure?)
Quite a long winded question so I appreciate anyone taking their time to read and thanking you in advance for providing any guidance
Without getting into your specific questions: if the client portal is a subpage of your main doc, there currently isn’t a way to prevent other users of your doc to see ANY page of your doc.
Coda has promised some improvements in this area and that should be released soon, but until we see and test this, the answer is negative.
If you are going to make separate docs for each client, you can set access yourself. But to share only client specific data from another central doc, things become quickly very complicated and I would advise against trying to set it up that way. Needless to say - this “another central doc” should not be accessible for clients.
I am hopeful that the changes that Joost mentions will be available in a matter of weeks rather than months.
I see this is your first post: I don’t know how much experience you have with Coda, but I would like to suggest that you play around with what is possible with the current functionality.
Your to-do list of project management and agency tracking can be come a huge topic, depending on the requirements. Research what is available in the gallery, try out your own ideas to see what works in your particular circumstances. Be prepared to restart at least three times!! Experiment with the idea of having a central document syncing pages to client portals, as well as the idea of having separate client docs, communicating back to a central document.
There are many, many different ways to accomplish what you are looking for, and it is always going to come down to what is the best for your specific circumstances.
Taking into account Coda’s announced project to enable limiting access to infomration.
Correct first post here with a basic understanding of Coda but definitely enjoy using the product.
I definitely restarted a few times already
When you say central document syncing pages to client pages, how would that be displayed exactly, I understand theoretically how it works but I am having trouble visualizing it,
The change that Joost and I referred to above is phase 3 of a 4 phase project that Coda is working on to allow certain information to be restricted from access.
When you create a new page in a doc, see below, you have the option to create a “sync page” from another, source doc. This was phase 2, and is currently in place. But you can still get from this new sync page in the new sync doc, back to the original source doc. The objective of phase 3 is that one will no longer be able to drill from the destination doc back to the source doc. The information between these two docs will be kept in sync though.
Basically you can have a big project table in the source doc, create new pages with project/client specific views of that project table. Create a client specific doc, sync to this client page in the source doc, and work together.
But as Joost said, subject to testing and verification.
Experiment with the idea of having a central document syncing pages to client portals, as well as the idea of having separate client docs, communicating back to a central document.
