Home
General concepts⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅎⁢‍⁢⁠‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‌⁢⁡⁢⁢‍‍⁡𝅗𝅥
Overview⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁢⁢‌‍‍⁡𝅗𝅥
Organizations and accounts⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥
The content schema⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁢⁢‍‍‍⁡𝅗𝅥
Organizing content⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁡⁢𝅳‍‍⁡𝅗𝅥
Roles and permissions⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁡⁢𝅎‍‍⁡𝅗𝅥
Collaboration features⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁢⁢⁢‍‍⁡𝅗𝅥
Localization⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢​‍‍⁡𝅗𝅥
Record versioning⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁢⁢⁣‍‍⁡𝅗𝅥
Draft/published system⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢‌‍‍⁡𝅗𝅥
Scheduled publishing⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁣⁢⁠⁢𝅎‍‍⁡𝅗𝅥
Media Area⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢‍‍‍⁡𝅗𝅥
Working with images⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢⁢‍‍⁡𝅗𝅥
Video encoding/streaming⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢⁢⁢⁠‍‍⁡𝅗𝅥
Environments⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅎⁢‍⁢⁠‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‌⁢⁡⁢⁢‍‍⁡𝅗𝅥
Workflows⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁣⁢​⁢𝅎⁢⁢​⁢‍⁢𝅳⁢‍‍‍⁡𝅗𝅥
Webhooks⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢⁣‍‍⁡𝅗𝅥
Plugins⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢⁠‍‍⁡𝅗𝅥
DatoCMS Site Search⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢‍‍⁡𝅗𝅥
How to deploy⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‍⁢⁢⁢𝅳⁢⁡‍‍⁡𝅗𝅥
Project/account usages⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁣⁢​⁢⁢​⁢⁢⁢​⁢𝅳⁢⁡‍‍⁡𝅗𝅥
Audit Logs⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁣⁢⁣⁢𝅎⁢𝅎⁢𝅳⁢​⁢𝅳⁢⁡‍‍⁡𝅗𝅥

    General concepts⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅎⁢‍⁢⁠‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢⁢⁢𝅎⁢𝅳⁢⁢⁢‌⁢⁡⁢⁢‍‍⁡𝅗𝅥 > Organizations and accounts⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    Organizations and accounts⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    When you create a new account with DatoCMS, you are creating a ⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥personal account. A personal account is your own, individual account, registered with the DatoCMS platform. It can hold personal projects and billing information.

    Organizations

    Projects on DatoCMS can also be tied to an organization. Organizations are useful to share the ownership of projects with other accounts.

    Similar to what is possible on personal accounts, organizations can also purchase paid plans, and hold separate billing information.

    There's no limit on the number of organizations you can create, or be invited to.

    Creating an organization

    You can create an organization by clicking on the scope selector in the top left of the nav bar. When you create a new organization, you will be prompted to give that team a name. This is the name your organization will have on your dashboard, and what other members will use to access your organization.

    Converting a Personal Account into a new organization

    At any time, you can move all projects, plan, credit card and billing information linked to your personal account, to a new organization. This can be especially useful for all those personal accounts created before organizations were available in DatoCMS.

    To convert your personal account into an organization, go into the Edit Account tab, and within the page select the option Move projects and billing information to a new organization.

    Your personal account will be switched to a free Developer plan, and the new organization will hold all of your existing projects and billing information.

    You will also become the first owner of the newly created organization.

    Organization members

    Organizations are made up of members, and each member of an organization can be assigned a role. These roles define what you can and cannot do within an organization on DatoCMS.

    DatoCMS currently offers two roles for your organization members. Let's review them:

    Owners have full privilege access to the entire organization. An owner can manage billing, change plan, invite other members to the organization, manage all projects settings, and enter every project with full privileges. They are also the only members that can destroy the organization.

    Organizations can have more than one owner!⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    To maintain ownership continuity for your organization, you should have at least two people with owner permissions. Adding additional owners will not remove any existing ownership.⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    Viewers cannot perform any action, but have complete read-only access to the organization. This role can be useful for people on your team who deal with finance/invoices/administration, so that they can download invoices and track costs, without making accidental changes to existing projects, or the organization itself.

    The table below summarizes the available authorizations for each role:

    PermissionOwner Viewer
    Read-only access to everything✅✅
    Enter all projects with full proviledges✅
    Create/edit/delete projects✅
    Transfer projects✅
    Manage members/roles✅
    Manage plan and billing✅
    Rename/delete organization✅
    Partner specific roles⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    Organizations that have been accepted through our ⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥partner program have access to additional roles to manage their projects across clients, as you can check out here

    Inviting new members

    To invite new members to your organization, select the organization from the scope selector, then open the Members tab. Enter the email address of the person you would like to invite, select their role, and click the "Invite" button.

    As the organization Owner, you can add new members, remove existing members, and change their roles. Members who have accepted an invitation to the team will be displayed as members with their assigned roles.

    Entering a project: Project owners vs. Collaborators

    Let's recap the ways in which one can enter a DatoCMS project:

    If the project is inside a personal account
    • The owner account always enters the project with full privileges

    • Accounts invited as collaborators within the project, enter with the permissions of the specific role they have been given

    If the project is inside an organization
    • Members of the organization with the Owner role enter the project with full privileges

    • Accounts invited as collaborators within the project, enter with the permissions of the specific role they have been assigned

    Collaborators take precedence over organization memberships⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    Within an organization, there is a further possibility worth emphasizing: if a member of the organization has also been invited as a collaborator, ⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥the role as collaborator takes precedence: they do not enter with full privileges, but with the permissions of the specific role they have been assigned as collaborator.

    Take, for instance, a case in which someone is responsible for billing matters but will not interact with content. In this case it would be reasonable for them to be an organization owner (so as to modify billing information) but to also be invited to the project as collaborator using a role with few privileges — probably read-only.

    Also consider a user who is totally in charge of a marketing website, but should not have power within the organization itself. This user should be invited as collaborator with full privileges to the project, but should be a simple Viewer at the organization level, if they are even to belong to the organization at all.

    Leaving an organization

    To leave an organization, select the organization from the scope selector, then open the Members tab. Find you account in the list of members, and then press the "Leave the organization" button.

    At least one member must be owner!⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    You can't leave an organization if you are the last remaining owner. To leave an organization, first assign the owner role to at least another organization member. ⁡𝅶‍‍𝅺⁡‍𝅎⁡𝅎𝅹‍‍⁢𝅵‍‍⁣⁣‌⁡⁣𝅺⁣⁢⁣𝅗𝅥⁠⁢‍‍‍𝅷‍‍𝅳⁡‍⁠‍‍⁢𝅵‍‍𝅳⁡⁣⁡⁣⁡​⁡⁢⁢𝅵‍𝅺‍𝅺⁢𝅗𝅥⁡⁢‍𝅹⁣‌⁡⁣𝅺⁢𝅗𝅥⁡⁢‍𝅹⁢𝅺𝅗𝅥‍𝅺⁠⁣𝅎⁡⁣𝅺⁡‍‍𝅺𝅎⁡⁣⁠𝅗𝅥⁠𝅺⁡⁣⁡𝅎⁡​⁠⁡⁢‍𝅺⁢𝅳⁢‌⁢​⁢𝅳⁢𝅎⁢‌‍𝅺𝅎⁡⁣⁠𝅗𝅥⁡⁢‍𝅺⁢‌⁢⁣⁢⁢‍⁢‌⁢𝅳⁢⁠⁢‍⁢‍‍⁡𝅗𝅥

    If you are the only remaining member, you should delete the team instead.