Decide for yourself who can reach your data
You share data with colleagues, chain partners and systems, and you decide who sees and may do what. Staff log in via your organisation’s account system. Systems log in with an API key that you set to expire. You manage roles and permissions per solution, page and component.
Share data with the parties who work with it
You share data via API integrations and exports, or process it automatically with the public Python package. You stay in control: roles and permissions determine who sees and may do what, per solution, page and component. You set those roles and permissions yourself.
The platform
This is where your data lives.
Roles and permissions
You decide per solution, page and component who sees and may do what.
The arrows run both ways: systems also write data back.
Staff
Chain partners
Systems
Via API and Python
You decide how data leaves the platform
Dashboards
Share insights with chain partners via dashboards and visualisations.
API
Systems add, replace, change or delete records via an open standard interface.
Python
With the public Python package you read, create, change and delete data from your own scripts.
Export
As Excel, CSV or JSON.
Restricted access
A chain partner gets read-only access, or only the pages and data that belong to their role.
From SSO to API keys with an expiry date
Staff
They log in via your organisation’s account system (single sign-on) or with their own password. A one-time code as a second step makes logging in more secure. If someone loses that second step, there is a recovery procedure.
Developers
Guides are available for connecting to your account system.
Systems
A system logs in with an API key. A key belongs to a system, not to a person. You set how long a key is valid: one day, 30 days or three months.
How a colleague gets access
Account
Your organisation’s administrator requests an account.
Role
The new user gets a role with permissions that suit the task.
Log in
The user logs in via the organisation’s account system or with their own account.
Work
The user sees the pages and data that belong to the role.
Who works with it
Organisation administrator
Requests accounts, assigns roles and keeps track of who has access.
Staff member
Enters and maintains data, and sees only what belongs to the role.
Team leader
Views figures and progress, and exports them for reports.
Chain partner staff member
Works with their own account in the pages that have been opened up for the partner.
Developer
Connects systems with an API key and the Python package.
Open standards and reuse as a starting point
Clappform takes part in developments in the Network of Local Digital Twins (NLDT), so that the platform works well together with other digital twins.
You can read which standards the platform supports on the Open standards and digital twin page.
Frequently asked questions
1
How do I share data with my chain partners?
Through dashboards, API integrations, the Python package or an export. With roles and permissions you decide what a partner sees and can do.
2
How do employees log in?
Through your organisation’s account system (single sign-on) or with their own password, optionally with a one-time code as a second step.
3
How long is an API key valid?
You set that yourself: one day, 30 days or three months.
4
Who gives a new colleague access?
Your organisation’s administrator. They request the account and assign a role.
5
Can a chain partner have view-only access?
Yes. A partner can get read-only access to the pages and data that belong to their role.
6
Can I see who did what?
Yes. The platform keeps an audit trail.
7
Does this support the GDPR?
The platform supports the requirements of the GDPR.