> For the complete documentation index, see [llms.txt](https://manual.senseforce.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.senseforce.io/manual/sf-platform/virtual-events/permissions-and-data-access.md).

# Permissions and Data Access

Just like in any other part of our application we ensure that users can only see the data they are supposed to see.

* You can define if a group has access to virtual events editor or not.
* A virtual event action is executed with the data the owner (initially the creator) has access to.
* Access to the data generated by virtual events is handled by giving access to the regarding things (just as for normal events). I.e. if you have a row of data where the thing is "machine A" only users with access to this thing can see this row.
* You can share virtual events separately with read or write permissions.

### Granting Access to Virtual Things

In a virtual event, you can assign any string column to the metadata thing attribute. If you do so the different entries will get registered as virtual things and will be available in the group settings.

![](/files/-MDUSeRDauQyQUO7b9QM)

If the thing is used exclusively in virtual events it will be marked as **virtual** in the group settings. If a user has access to a certain thing, he will be able to see and use the data related to this [thing](/manual/sf-platform/user-and-group-management.md#things) (regardless of whether it is virtual or not).

{% hint style="warning" %}
If a virtual event creates data of a thing that didn't exist in the database before the normal user will not see this data until the admin assigned permission for this thing to the user! This also holds true for virtual events which the user created by itself!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manual.senseforce.io/manual/sf-platform/virtual-events/permissions-and-data-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.