Datacake Docs
  • Welcome
  • Get Started
  • Changelog
  • Best practices
    • Best practices: Getting started
    • Best practices: Resolution (Timeframe)
    • Best practices: Dashboards
    • Best practices: Reports
    • Best practices: Grouping Devices
  • Datacake LNS
    • Getting Started
    • Gateways
      • Milesight LoRaWAN Gateway - UG6x
      • RAKwireless WisGate Edge Light 2
    • Devices
    • Add Devices without Gateway
  • Device
    • Product
    • Configuration
    • Claiming
    • Historical Data
    • Database
      • Configuration Fields
      • Fields
        • Manual input
        • Field Roles
        • Formulas
        • Mapping Fields
      • Data retention & Datapoints
      • Examples
        • Mapping 4-20mA Signals
        • Converting Units
  • Dashboards
    • Global Dashboards
      • Setting Homepage
    • Device Dashboards
    • Multi-Device Dashboards
    • Widgets
      • Value Widget
      • Chart Widget
      • Image Map
      • Map Widget
      • Text Widget
      • SOS Widget
      • Boolean Widget
      • iFrame Widget
      • Downlink Widget
      • Set Value Widget
      • Measurement List Widget
      • Heatmap Widget
      • Table Widget
      • Image Widget
  • Portal
    • Multi-Tenancy (Workspaces)
    • Reports
      • Energy Report
    • Administrators
    • Members
      • API Users
    • Security & Privacy
    • Billing
      • Support Packages
      • VAT Exemption / Tax ID
      • SMS Credits
      • Access Invoices
      • Unused time and Remaining time in Invoices (Prorations)
      • Codes
    • White Label
    • Rules
      • Legacy Rule Engine
        • Sending notifications via Telegram
      • New Rule Engine
        • Rule Engine Table Overview
        • Copy/Paste and Template Functionality
        • Advanced Rule Engine E-Mail and Webhook Templates
        • Time Restrictions
    • Zones
  • Cake Red
    • Get Started
    • Overview
  • LoRaWAN
    • Get Started
      • CSV Import
      • Custom LoRaWAN Device
    • Configuring LNS
      • The Things Stack (TTN / TTI) Automated Setup
      • The Things Stack (TTN / TTI) Manual Setup
      • Loriot
      • Kerlink Wanesy
      • Helium
      • ChirpStack
      • Tektelic
      • Actility ThingPark
      • Senet
      • Milesight Gateway
      • KPN
    • Downlinks (LoRaWAN)
      • Set Time Frame
    • Securing Webhooks
    • Payload Decoders
      • Location and GPS
      • Access Gateway Metadata
      • Access Measurements
      • Global Variables
    • Using Cayenne LPP
    • Converting Payload
  • Generic API Devices
    • HTTP Downlinks
  • Integrations
    • MQTT
    • Particle
      • Get Started
      • Adding Integrations
      • Decoding Payloads
      • Calling Functions
      • Templates
        • Particle Tracker One
    • Incoming Webhooks
    • Outgoing Webhooks
      • Securing Outgoing Webhooks in Datacake
    • Golioth
    • Blues Wireless Notecard
    • Sigfox
    • Swarm Asset Tracker
    • Grandcentrix Modbus Cloud Connect
    • YuDash LYNX IoT Gateway
    • Dragino NB-IoT
      • Changing NB-IoT Bands
    • Hardwario CHESTER
    • 1NCE OS
  • API
    • Exporting Data
    • Record Measurements via API
    • Node RED to Datacake
    • Generate Access Token
    • Internal MQTT
      • Get Started
      • MQTT Documentation
      • MQTT over WebSocket
      • Example Code
    • GraphQL API
      • Using GraphQL
      • Device Creation
      • Tutorials
        • Read Group via Tags
  • Guides
    • Python
    • Send Slack Notifications
    • Forward Data to Cake Red
    • Multiple Data Feeds
    • Automated Dynamic Downlinks
    • Ingesting JSON Data into Datacake API Devices
    • Working with Default HTTP Decoder on API Devices and Code Examples
    • Accessing Measurements in Decoders
    • Connecting Datacake to Notion Using Zapier
    • How to set up and use location on non-GPS devices
    • How to integrate with AWS IoT Core
    • How to Schedule Mass-Downlinks (Multicast) using Datacake Rule Engine
    • How to Map Sensor Values to Ranges or Booleans, Strings using Mapping Fields
    • Understanding Internal vs. External MQTT Brokers on Datacake
    • Sending UDP Messages between 1NCE OS and Datacake
    • Concepts of LoRaWAN Payload Decoders on Datacake
    • How to check if a value stays above or below limits for given time
Powered by GitBook
On this page
  • What are Members?
  • Different Types of Members
  • Add a new Member
  • Invite via E-Mail
  • Set Workspace permissions
  • Add Devices
  • Set Device Permissions

Was this helpful?

  1. Portal

Members

Last updated 8 months ago

Was this helpful?

What are Members?

Members are User-Accounts that have access to a given Workspace. You can add multiple members into your workspace and define rights and roles and the devices the user is allowed to see, control, change.

For a step-by-step guide on our Members section, be sure to check out our video tutorial ⬇️

Different Types of Members

Currently there are two types of Members:

  1. Normal Users - which are physical Users that have a User-Account on the Datacake Plattform and that log in using E-Mail / Password combination.

  2. API Users - which have the same mechanisms like rights and role management for devices and functions but instead of having a user-account, API users can be created dynamically and provide a Token that you can use for the REST-API or Datacake MQTT Broker.

Read more about API Users here:

Add a new Member

To invite new members to your workspace, use the sidebar to navigate to the "Member" item under the "Administration" group. You should now see the following content in your browser

To create a new member, click on the button "Add Member". You will find this button in the upper right corner of the "Members" panel. The following dialog will then appear:

Invite via E-Mail

You always add members by entering the e-mail of the desired user. This user will then receive an invitation by e-mail, which he/she must confirm in order to finally register.

If the invited person is already a member of the Datacake platform, they will be added to your workspace immediately.

Set Workspace permissions

With the workspace permissions you control what rights the user has in your workspace. Basically, you can define here very finely what is allowed - and what is not. However, you do not necessarily have to activate an option and can invite the user to the platform as an "observer".

The following workspace permissions are currently available for selection:

Basic

Sets basic permission to edit the name and logo of the current workspace.

Billing

This option gives the user access to the statements, invoices and payment settings in your workspace.

Devices

If this option is activated, the user may create new devices or remove existing ones.

Members

By activating this option, the user can also invite or remove other members, create or remove own teams and define permissions.

Workspaces

Activate this option if you want the user to be allowed to create their own workspaces.

Rules

Allows the user to use the rule engine and create, edit and remove rules for devices.

Add Devices

At the time of inviting a new user, you can already determine which devices the user is allowed to access.

To do this, simply type the device name into the search field below "Device Permissions" and confirm the device you are looking for by clicking on it in the search results.

Set Device Permissions

Once you have selected the device(s), a new panel appears in the dialog for each device. Here you can define the rights for the respective device and thus determine what the newly invited user may do with the device:

Can view the Device and its data

This permission is always activated. It allows the user to view - but not edit - the device and its measured values.

Can edit the device definition

Allows the user to customize general settings like name, location and description.

Can edit device metadata

Specifies that the user may modify the metadata and create his own metafields.

Can record measurements

If this option is activated, the user can set measurement data via his token (API or MQTT) or the manual input of measured values.

API Users