Admin Guide

Synapse-Intel471 Admin Guide

Configuration

Synapse-Intel471 requires an Intel471 API key. For information on how to sign up, please visit the Intel471 website.

Setting API key for global use

To set-up a global API key:

> intel471.setup.apikey myapiemail myapikey
Setting Intel471 credentials for all users.

Using per-user API keys

A user may set-up their own API key:

> intel471.setup.apikey --self myapiemail myapikey
Setting Intel471 credentials for the current user.

Setting a tag prefix for global use

Note: If not set, this will default to rep.intel471.

> intel471.setup.tagprefix my.prefix
Setting Intel471 tag prefix to my.prefix.

Dependencies

Synapse-Intel471 does not have any dependencies.

Permissions

Package (synapse-intel471) defines the following permissions:
power-ups.intel471.user          : Controls user access to Synapse-Intel471. ( default: false )

You may add rules to users/roles directly from storm:

> auth.user.addrule visi power-ups.intel471.user
Added rule power-ups.intel471.user to user visi.

or:

> auth.role.addrule ninjas power-ups.intel471.user
Added rule power-ups.intel471.user to role ninjas.

To customize the tag prefix applied to nodes, Synapse-Intel471 requires the permission globals.set.intel471:tag:prefix to be set on the user/role. You may set this perm to users/roles directly from storm:

> auth.user.addrule visi globals.set.intel471:tag:prefix
Added rule globals.set.intel471:tag:prefix to user visi.

or:

> auth.role.addrule ninjas globals.set.intel471:tag:prefix
Added rule globals.set.intel471:tag:prefix to role ninjas.

Exported APIs

Synapse-Intel471 does not currently export any APIs.

Workflows

Synapse-Intel471 provides the following workflows in Optic:

Title: Configuration

Onload Events

Synapse-Intel471 uses an onload event to add extended model forms and properties for Intel471 data, and run any required data migrations.