Senseforce 2.0 Manual
  • Welcome to Senseforce 2.0
  • SF MQTT API
  • SF Edge
    • Edge Package Overview
    • Edge Installation
      • Using the SF Edge Service installer in command shell
      • Headless SF Edge Servie execution
    • Edge Configuration
      • Which Plugins to load (appsettings.xml)
      • Edge Data Routing (EventDefinition.xml)
      • OTA configuration (otasettings.xml)
      • Edge Logging
      • Input plugins
        • SQL Plugin
        • SQLite Plugin
        • OPC UA Plugin
          • OPC UA server browser
        • SIEMENS S7/SINUMERIK Plugin
          • Creating connection definition file
        • S7 Plugin
        • REST Plugin
        • TCP Listener Plugin
        • XML File Parsing Plugin
        • Heidenhain Plugin
      • Output Plugins
        • MQTT Plugin
        • SQLite Plugin
    • Edge Compute plugins
      • Creating compute plugins
      • Using compute plugins
  • SF Edge Asset Management
    • Edge version repository
  • SF Platform
    • Navigation
      • Overview Screen
    • Dataset Builder
      • Filters, Aggregations and Groupings
      • Functions of the Formula Editor
      • Additional Settings
      • Special Events
      • FAQ and Troubleshooting
    • Script Editor
      • Details of the Script Editor
      • Installed Packages
      • Working with Timestamps
        • Working with Timestamps in Python
        • Working with Timestamps in R
      • FAQ and Troubleshooting
    • Widgets
      • Text
      • Headline
      • Image
      • Progress Bar & Gauge Chart
      • Table
      • Map
      • Line, Bar, Scatter and Area Chart
      • Pie Chart
      • Gantt Chart
      • Histogram
      • Overview
      • Log
      • Default colors and color conditions
      • FAQ and Troubleshooting
    • Dashboards
      • Dashboard Filters
      • Favorites
      • Data Drilldown & Widget Interaction
      • Editing multiple dashboard widgets
      • Time Zones
      • Synchronized Zooming
      • Sharable Dashboard URL
      • Multi-chart layout options
      • Default sort for table widgets
      • Releases
      • Reporting
      • FAQ and Troubleshooting
      • Applying zoom to global timestamp filter
      • Optimise the layout for different devices
    • Machine Master Data
      • Dimensions
      • Instances
      • Things
      • Use Case
      • FAQ and Troubleshooting
    • Automation
      • Trigger
      • Scheduling overview
      • Actions
      • Test your Automation
      • Zapier integration (necessary internal steps)
      • Zapier integration
      • Subscriptions
      • FAQ and Troubleshooting
    • Event Schema Management
      • Importing a Event Schema
      • FAQ and Troubleshooting
    • Virtual Events
      • Creating a Virtual Event
      • Scheduling Overview
      • Permissions and Data Access
      • FAQ and Troubleshooting
    • Details modal for elements
    • Copy / Duplicate elements
    • Whitelabeling
    • Edge Device Management
    • Element History
    • Public API
      • Get your access token
      • Endpoints
      • Debugging scripts
      • FAQ and Troubleshooting
    • User & Group Management
      • FAQ and Troubleshooting
    • Active Directory & SSO Setup
Powered by GitBook
On this page
  • I can not share my automations in the group management!
  • It looks like someone with read permissions for an element can change it!
  • A user of the same group can not see all the elements I see, why?
  • A user has write permission but can not change an element!
  • A user has read permission but can not see an element!
  • Are elements I create also shared with all other users in my group?
  • If I have write permissions do I automatically also have read permissions?
  • An element was shared with my group but I do not have access to this part of the application.
  • If I share a dashboard do I also have to share all used sub-elements?
  • Who is the super-admin and what is he allowed to see?
  • What is a good practice to create a user & group management system?

Was this helpful?

  1. SF Platform
  2. User & Group Management

FAQ and Troubleshooting

PreviousUser & Group ManagementNextActive Directory & SSO Setup

Last updated 3 years ago

Was this helpful?

I can not share my automations in the group management!

This option is not yet available, please share your automations via the overview of the automations, like in the following picture,

It looks like someone with read permissions for an element can change it!

A user can access an element he has read permissions for and in this view mode he can change the element but he is not able to save the changes.

A user of the same group can not see all the elements I see, why?

Either you are also part of a different group that has access to other elements or there are elements you own (because you created them) that were not shared with the group.

A user has write permission but can not change an element!

A user has read permission but can not see an element!

Are elements I create also shared with all other users in my group?

If I have write permissions do I automatically also have read permissions?

An element was shared with my group but I do not have access to this part of the application.

In this case, you can not look at this element directly. But let's say you do not have access to the dataset and script editor. If a script or dataset is shared with you, you can use it in a widget, but can not access it directly.

If I share a dashboard do I also have to share all used sub-elements?

For the dashboard to work as it is, no. But the user will not be able to alter the sub-elements and if this user removes a sub-element (e.g. a widget) that was not shared with him, he will not be able to add it to the dashboard again.

Who is the super-admin and what is he allowed to see?

Usually, there are two super-admins one is owned by Senseforce, in case we need to investigate problems on your platform, and one is owned by a member of your company.

The super-admin has write access to all elements and access to all things on your platform.

What is a good practice to create a user & group management system?

As soon as you are starting to get more than just a couple of users it is important to think about a concept for your user management.

There are basically three dimensions in our permissions system, i.e. access to things, components, and elements. If you think of every user in terms of these dimensions you will get lean and understandable group management.

Example

In terms of thing-permissions, you need to consider that you have two customers, which are only allowed to see their machines. Hence you create two groups with permissions to the machines of each customer (and maybe a group for internal users with access to all things). You might also have different roles, like manager and technician. The manager group should have access to the organisational dashboards and the technician to the technical ones. So one group with access to the respective elements for each role. At last, you might have different types of users, some might only need to view content, some need to create content. Create groups with different permissions in terms of the platform components. Now let's say we have a technician from customer 1 who needs to create widgets and dashboards. You can assign him to the groups "Customer 1", "Technician" and "Creator" and he/she will have all the necessary permissions.

If you want a user to be able to change an element make sure the element is (with write access) with one of his groups and that he has for this part of the application.

If you want a user to be able to see an element make sure the element is (with read or write access) with one of his groups and that he has read or write for this part of the application.

No, you need to explicitly an element with groups, even with the ones you are part of.

Yes, if you have write for a component of the platform or an element you also have read permissions.

shared
write permissions
shared
permissions
share
permissions
Example for assigning different groups to different users.