Starting from a template

What a template is

A template is a ready-made project — its pages, dashboards and files already in place. Starting from one copies the whole thing into a new project of your own. You work in the copy; the template itself is not something you edit.

Templates are in the application, under Templates in the sidebar. What is in the gallery is whatever has been provisioned for the deployment you are signed in to, so this page does not promise you a particular template — only what happens once you pick one.

One click, one project

Each card names a template and what it contains. Use template starts it.

The button disables and reads Creating… while the request runs. It is one request, issued once, and it finishes in the foreground — there is no background job to come back and check on later. When it returns you are already on the new project's home, at a project that did not exist before you clicked.

That busy state is also the guard against a double click. Wait for it rather than clicking again — two clicks would be two projects.

The new project takes the template's name. Start the same template twice and you will have two projects called the same thing, so rename one if you meant to keep both.

What lands in the project

Every item the template carried — its pages, dashboards and files — arrives in your project at the same relative path it had in the template, the README included. A template listing four items gives you a project holding those four items: nothing extra, nothing missing. Uploaded files come across as files, not as links back to the template.

What does not come across is history. A copy carries the items themselves, not their past versions, their previous runs, or the conversations that happened in the template. You are starting those from the beginning, in your own project.

What you are working in afterwards

The new project also becomes the project you are working in. The switcher in the sidebar moves to it as the page redirects, so the next thing you do in the application — a chat turn, a new page — is written into the project you just created rather than the one you were in before.

If starting one does not work

An empty gallery means no templates have been provisioned for the deployment you are signed in to. There is nothing to fix from your side; ask.

If a card is there and starting it fails, the application says so and you stay on the gallery with no new project made.

What a template is not

It is not a subscription to the original. Once your project exists, nothing connects it back to the template it came from. Later changes to that template do not reach a project already started from it, and there is no version of a template to track.

You cannot publish one. Templates are provisioned into a deployment; a project you have built is not something the application lets you offer back to the gallery.

It is not a route around access. You reach the application through an NSGPT engagement and no other way — request a demo — and what you connect it to is covered in Connecting your NetSuite account.