# Create own custom templates for spaces **URL:** \ **Category:** Bugs & Issues\ **Created:** [April 17, 2022, 8:12am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717 "2022-04-17T08:12:30Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 17, 2022, 8:12am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/1 "2022-04-17T08:12:30Z")
Is that possible to create own custom space templates? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 17, 2022, 9:01am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/2 "2022-04-17T09:01:23Z")
What do you mean? You can create a Space and share it with the world. There is no unified gallery to collect all shared templates so far. > **[Share your Space](https://help.fibery.io/en/articles/4693262-share-your-space)** > > Clone Spaces from one workspace to another, create templates and don't struggle alone đź’Ş ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 17, 2022, 10:15am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/3 "2022-04-17T10:15:22Z")
We have a workflow for software dev process. For new projects we create a new space. Right now we manually create all databases, fields, etc. I would be great to have our own template to exclude manual work. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 17, 2022, 12:33pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/4 "2022-04-17T12:33:01Z")
I see, now you can’t import Space into the same Workspace. We will fix it ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 17, 2022, 3:28pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/5 "2022-04-17T15:28:09Z")
If you export a space as a template, you can reimport it, provided you change the name of the original space (after generating the space sharing url). Once the new, cloned space has been imported, you can change its name to whatever you like (and give the source space its original name) if you wish. It sound complicated, but it boils down to always ensuring no two spaces have the same name. ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 17, 2022, 4:32pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/6 "2022-04-17T16:32:51Z")
Sorry but it should be done easier for the end user. I guess additional category with custom templates will do the job. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 17, 2022, 4:44pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/7 "2022-04-17T16:44:41Z")
From what you wrote, it sounds like you need an easy way to clone an existing space within a workspace, rather than the ability to store custom templates alongside Fibery-produced templates. If a naming conflict could be detected and resolved/avoided at the time of import, the current mechanism (share as url and import) would be fairly simple don’t you think? ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 17, 2022, 5:18pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/8 "2022-04-17T17:18:15Z")
> [@Chr1sG](#): > > If a naming conflict could be detected and resolved/avoided at the time of import, the current mechanism (share as url and import) would be fairly simple don’t you think? It does. What I’m trying to say your suggestion sounds more like a workaround. From the user perspective I tried to find a way to save a space as a template. Anyway, thanks for helping. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 17, 2022, 8:44pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/9 "2022-04-17T20:44:50Z")
> [@Eugene\_Vabishchevich](#): > > your suggestion sounds more like a workaround Oh yeah, it definitely is! 🤷‍♂️ Just out of curiosity, to understand your need better…for these new project spaces, would you want to be able to clone an existing space but without its entities, or would you need to have a new space setup with some predefined entities? Also, what is driving the decision to create a new space per project? Is there something that could be improved that would enable you to manage multiple projects within the existing space? ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 18, 2022, 6:08am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/10 "2022-04-18T06:08:24Z")
> [@Chr1sG](#): > > Just out of curiosity, to understand your need better…for these new project spaces, would you want to be able to clone an existing space but without its entities, or would you need to have a new space setup with some predefined entities? We need just one new space without entities. But database, fields, buttons should be in place. > [@Chr1sG](#): > > Also, what is driving the decision to create a new space per project? > Is there something that could be improved that would enable you to manage multiple projects within the existing space? We have many projects with different level of access. Currently it’s not possible to share access to entities/documents/folders between users. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 18, 2022, 7:30am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/11 "2022-04-18T07:30:55Z")
As I understand, this problem will be solved when we will add per-entity access? ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 18, 2022, 7:43am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/12 "2022-04-18T07:43:01Z")
I hope so. Do you plan to extend folders with access feature? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 18, 2022, 7:43am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/13 "2022-04-18T07:43:59Z")
Unlikely, since Folders are not usual entities. But we will discuss this option as well ---
**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\ **Post date:** [April 18, 2022, 8:00am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/14 "2022-04-18T08:00:15Z")
If it’s possible to close this one as well it will be very helpful: [Link to the folder](https://community.fibery.io/t/link-to-the-folder/1632) ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [April 18, 2022, 10:30am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/15 "2022-04-18T10:30:33Z")
We had the same problem and the only workaround is changing the name which is more like a bug than workaround. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 18, 2022, 10:54am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/16 "2022-04-18T10:54:47Z")
> [@Jean](#): > > changing the name which is more like a bug than workaround To be fair, the choice to not allow different spaces to have the same name is arguably a design decision rather than a bug. But yes, when importing a new space, if there is a name clash, then resolving this gracefully (e.g. inviting the user to choose what names the original/new space should have) rather than refusing the import would be an improvement, no doubt. ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [April 18, 2022, 11:30am UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/17 "2022-04-18T11:30:58Z")
When you click “Share as template” and you put a different name there, every user will expect that the new space has that name and not get an error. Very few will thnnk that you have 2 different namings, one for the template and one for the space. Even on the Templates section of Fibery, template names have the same names as the spaces so it’s obvious to assume that by template name you mean the space name. ---
**Author:** ![danex](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@danex](https://community.fibery.io/u/danex)\ **Post date:** [July 12, 2023, 3:34pm UTC](https://community.fibery.io/t/create-own-custom-templates-for-spaces/2717/18 "2023-07-12T15:34:16Z")
Agreed, just ran into this exact situation! Thanks all for the thread and the workaround above.