Skip to content

Create A Data Access Request From A Template

This guide walks through creating a data access request from an existing template, entirely through the dashboard — from picking the template, to approval, to activation, to actually querying the data. No API calls are needed for any of this.

If you don’t have a template yet, see Before You Start below, or Import & Export Request Templates to load a whole set at once.

Templates live on the Request Templates page. To get there:

  1. Open Data Requests from the main navigation.
  2. Click From Template.

You’ll land on Request Templates, with the breadcrumb Data Requests > Request Templates at the top. Each saved template is shown as its own card. If none exist yet, you’ll see an empty state inviting you to create one — a template is really just an existing request saved for reuse, so the fastest way to get your first one is to build a normal request once and save it as a template from there. To build that first request:

  1. Open Data Requests and click New Request.
  2. On What kind of access do you need?, click Data Enclave. This is the type this guide uses. Data Proxy is only available once the deployment has a proxy password key (see Standalone Bundle Install); until then it shows “Requires configuration”. Clicking a card moves straight on to the next step, so don’t also click Next, which would skip past the Source step.
  3. A Data Enclave request then shows the Source step, How would you like to create this request? (a Data Proxy request and a request from a template don’t). Choose Create manually, which also moves on; it’s already selected, so Next does the same. Import from ticket needs a ticketing integration, and Create with AI appears only when AI is enabled on the deployment.
  4. On Details, fill in Request Name and Validity Period, which sets how long the access lasts (for example 1 hour). Both are required. Description and business justification are shown to whoever approves the request.
  5. On Data Sources, pick the datasource and tables. Ticking a table ticks all of its fields; untick the ones you don’t need (Select all ticks them all again). A datasource with more than 30 tables has a Filter box above the list, and a long list shows 100 tables at a time with Show more at the end; tables you’ve already ticked stay on screen whatever you filter by. A request can include several datasources: tick each one and its tables, and every selected table loads into the same environment. When two datasources have a table of the same name, the datasource’s name goes in front of the table names of both (see Loading Files Into A Request). Next stays disabled until every ticked table has at least one field; see When Next Is Enabled. For an SSH datasource whose files are dated, you also pick the days to load; see SSH Datasources: Dates And Files. An SSH datasource that an administrator still has to update after an upgrade shows Needs an update by an administrator and can’t be picked.
  6. On Review & Submit, check the summary and click Submit for Approval. The request appears in the Data Requests list as pending, and from there it follows Step 4 onward below.

The wizard may also show “Risk policy is not configured”. That only means risk scoring is switched off on this deployment (see Standalone Bundle Install). It doesn’t stop you submitting.

On the Request Templates page, find the template you want and click its Request button.

This opens the request wizard already pointed at that template. Because the template defines a fixed, pre-approved data scope, the wizard skips straight to the Details step — you won’t see the earlier steps where you’d normally pick a request type or a datasource from scratch.

The wizard shows a note at the top confirming which template you’re using, and makes clear what you can and can’t change:

Template: {template name} — Data scope is defined by this template. Title, description and justification are yours to edit.

Everything about what data the request touches — the datasource, tables, columns, filters, and the request’s validity period — comes from the template and can’t be edited here. What you can fill in or change:

  • Request Name — a short, specific title. The placeholder suggests something like a ticket number or a one-line description (e.g. “SNOW 1234, Lottery data for Marketing”); a distinct name makes the request easier to find later.
  • Description — what you need the data for, in your own words.
  • Business Justification — the business reason for this specific access, shown to whoever approves it.
  • External Ticket ID and External Ticket URL (optional) — link the request to a support ticket, incident, or project tracker entry if you have one.

If you change your mind about the title, description, or justification and want to start over from the template’s original wording, click Reset to template.

Click Next to move through the remaining steps. The Data Sources step is shown for confirmation only — it displays the datasets the template scopes you to, but the fields are locked and can’t be edited from here. If the template asks for values, such as a date window, a Request parameters card above it is where you enter them (see Request Parameters For Dated Files).

The final step, Review & Submit, shows a summary of everything the request will contain. Check it over, then click Submit for Approval.

You’ll see a confirmation (“Request submitted successfully”) and land back on the Data Requests list, where your new request now appears with a pending status.

Open the request from the Data Requests list to see its detail page. While it’s waiting on a decision, its status badge reads pending.

An admin reviews the request from the same detail page and either approves or denies it there — see Approve And Manage Requests for what that review looks like from the approver’s side. Once approved, the status badge changes to approved; if it’s turned down, it becomes denied.

Once a request is approved, its detail page shows an Activate button. Clicking it opens a confirmation (“This will provision a data environment for this request. Are you sure?”) — confirm to proceed.

The status badge moves through activating (shown as a disabled “Provisioning…” button) and then to active. For requests built on top of a datasource snapshot (the default, “enclave” type — see the note below), a second badge tracks the data load itself, moving from a loading indicator to data ready once the environment has everything it needs.

Once the request is active and its data shows data ready, its detail page shows an Explore data button. Click it to open the Data Explorer, already scoped to this request.

Inside the Explorer, the Query card gives you two ways to ask for data:

  • The SQL tab, with a text box where you can write a query directly (for example, SELECT * FROM customer_segments LIMIT 50; each approved table is named by its table name alone, such as ORDERS for an Oracle table, with no owner prefix; each SSH schema is one table named by the Table name the administrator gave it, such as APP_LOGS (with the datasource’s name in front only when two tables would share a name; see Loading Files Into A Request); an S3 file is named after the file, with a T_ prefix on names that start with a digit, see How File Names Become Table Names; the Available Datasets panel lists every name) and a Run Query button.
  • The Natural Language tab (when available on your deployment), where you describe what you want in plain language and either Run Query directly or Convert to SQL first to see the generated query before running it.

Either way, you’re limited to the data the template’s scope approved — there’s no way to reach beyond it from here. Results appear in a Results panel below the query box, with row counts and a paginated table.

If you need to reach the request’s data or Explorer from outside the network the dashboard is on, open the request’s detail page and click Create Tunnel. A confirmation explains what this does: it opens a public tunnel with a temporary API key and basic-auth credentials.

After confirming, a Tunnel Credentials dialog appears once, showing the Public URL, Data Explorer URL, API URL, and the issued credentials — copy anything you need now, since the full credentials aren’t shown again (a masked version stays visible afterward). From then on, the request detail page shows an Open Tunnel button to jump straight to the tunneled Explorer, and a Disable Tunnel button to shut the public endpoint down when you’re done with it.

If you no longer need the access before it expires on its own, open the request and click Revoke. You’ll be asked to type “revoke” to confirm — this immediately ends the request and tears down its environment.

When a request was denied, was revoked or has expired, you don’t have to rebuild it. Open it and click Request again: the form opens with what the original asked for, ready to change and submit. See Request Again.

When Next Is Enabled On The Data Sources Step

Section titled “When Next Is Enabled On The Data Sources Step”

In a request you build yourself, Next on the Data Sources step stays disabled until all of these hold:

  • At least one datasource is added with at least one table ticked. Ticking a table ticks all of its fields.
  • Every ticked table has at least one field ticked. Unticking a table’s last field removes the table from the request.
  • Every join you added has its second table and both join fields filled in.
  • If a filter takes a value from the request parameters, that value is filled in.
  • For a dated SSH schema, the dates are a valid range ending on or after their start, and the range selects at least one file for that schema and stays within the size limit; see SSH Datasources: Dates And Files. A schema whose files carry no date loads whole, so it blocks Next only when its files add up to more than the size limit, and a schema that can’t load is shown as not selectable.

A table with no field ticked is the usual reason Next is grayed out; the fix is to tick a field on it, or untick the table. When you build a template, dates that are still DATE [name] parameters don’t block Next, because the requester fills them in later; a request needs actual dates.

An SSH datasource lists its accepted schemas on the Data Sources step (see Schemas In The Catalog), and each schema you tick loads as one table, named by the schema’s table name. When the files’ names carry dates (see Dated Files), a Dates panel (“for every checked schema below”) above the schema cards sets which days to load:

  • From and To, both included.
  • Shortcuts Latest day, Last 3 days, Last 7 days and All. They count back from the latest day the datasource has files, not from today. In a request you build yourself, the range starts on Latest day; in a request from a template that lets the requester pick the dates, it starts empty (see Request Parameters For Dated Files).
  • A total such as 3 days · 2 tables · 14 files · 48.2 MB.

Each schema card shows the schema’s table name, a strip with one cell per day the datasource has files (in the range, outside it, or missing for this schema), and the number and size of the files the range selects. If a day inside the range has no files for that schema, the card says so, for example “No files for Sun 1 Nov; the other 2 days load.” Use different dates gives that schema its own From and To (marked own dates); Use the shared dates puts it back on the panel’s range. A schema whose files have no date in the name reads “No date in the name · loads whole” with its file count, and ignores the range.

A schema can’t be ticked, and blocks Next, when the range selects no files for it or its files add up to more than the deployment’s size limit (256 MB per table by default; see Persistent Platform Configuration). Narrow the dates or untick it. Select all tables skips such schemas. A range over the warning limits (100 MB or 31 days by default) is allowed, but the warning is shown on the schema, on Review & Submit (under Dated schemas, with each schema’s dates, files and size), and to the approver.

The request keeps the exact list of files the wizard showed. A file that appears on the host later, such as the next day’s log, isn’t added to this request; create a new one to load it.

When you build a template (New Template), the same Dates panel has a Requester picks the dates switch, on by default: the template then asks whoever uses it for From and To. Turn it off to fix the dates in the template. A schema’s Use different dates in a template always holds fixed dates.

Only files that fit a schema the datasource accepts are loaded; the others are skipped (see Skipped Files). When the datasource has skipped files dated inside the dates you chose, or skipped files with no date, whose schema isn’t accepted or that are too large to check, a warning appears under the schema. Files that could not be read aren’t counted there; they are listed only on the datasource page. It reads, for example:

3 files in these dates are left out: their schema is not accepted on the datasource. Ask an administrator to accept it on the datasource.

For a single file it reads 1 file in these dates is left out: its schema is not accepted on the datasource, followed by the same request to ask an administrator. A skipped file belongs to no table until its schema is accepted, so the warning isn’t tied to one table: it appears under every selected table of that datasource whose dates include the day of a skipped file, and a skipped file with no date in its name counts for every table. Giving a table its own dates that leave out that day (Use different dates) removes the warning from that table. The request stores the warning on the tables whose dates include the day. The warning doesn’t stop you submitting the request, and it is stored with the request, so the approver sees it too (see What You See When Reviewing). To load those files, ask an administrator to accept their schema; a request created after the next scan includes them.

A request template names a schema of the datasource. When you open a template whose schema the datasource doesn’t have, the dashboard applies the rest of the template and shows a notice, <dataset> was not found in <datasource>. Ask an administrator to update the template.. When the template includes a datasource that still has to be updated after an upgrade, that datasource is left out and the notice reads <datasource>: Needs an update by an administrator. Under the notices a sentence says A request can't be created from this template until it is updated., and the submit button is disabled. When you open an existing template to edit it instead, saving stays possible, and the sentence reads These datasets will be removed from the template when it is saved. If a request is created through the API for a schema the datasource doesn’t accept, it is refused with schema "APP_LOGS" not found in datasource "log-host", and for a datasource that still has to be updated with datasource "log-host" must be updated by an administrator before it can be requested. A single-file source (kind = "path") on an SSH datasource is refused with datasource "log-host" loads files through its schemas: use kind "path_list" with a schema name.

When a template lets the requester pick the dates, the Request parameters card on the Data Sources step shows one Dates row: From → To, the same shortcuts, the span the files exist in (“Files exist from … to …”), and the schemas the dates apply to. From and To start empty, unlike the Latest day default of a request you build yourself: fill them in, or click a shortcut such as Latest day, before Next is enabled. If the range is outside that span, the row warns that there are no files in these dates.