We’re pretty new to Tape, coming from Podio, and tend to use a couple of template workspaces to create new workspaces that are identical but for separate projects. I can’t see any way currently to create workspace templates only use the ones provided by Tape, possible feature request maybe?
In an attempt to workaround that, I’ve created a workspace called “Template XYZ” with the apps setup as required so that users can duplicate the template, rename it and start working. Unfortunately, when they try and duplicate the workspace template they get a “duplication failed - please try again” message each time.
The users in question are members of the organisation rather than org admins as they don’t need that level of permissions and I have any org member able to create workspaces set in the organisation settings. Duplication of the template workspace works fine for me as the Org Admin.
Is the duplication failed message a permissions thing or something I’m doing wrong? Is there a better way to achieve what we need?
first of all a very warm welcome to the Tape community. Happy to have you here!
The normal way to create workspace templates on Tape is via the publish to web option within the workspace settings. These are currently not published in the template market, but you get a web link with which anyone you provide the link to can duplicate the template in Tape - also in other Tape organizations. For example, we store several internal templates in an app and each record is a template with the link to it.
The approach you have chosen can also work very well. The users can also only duplicate workspaces where they are admin, so you can limit the possibility to duplicate to templates.
And you did everything right, I immediately tried to understand the problem and found out that once the option is enabled that a normal member can create workspaces, duplication is still not possible - this is actually a permission bug where a flag is set incorrectly. But my colleague is currently fixing the issue.
So in the end I think there are these two ways and in any case you need the setting that normal users can create workspaces. The first way already works because only the duplicate in the organization has the wrong permission flag.
The other way should also work correctly today, at the latest tomorrow.
Sorry for the issue and I will report here when the permissions are set correctly in this case.
