Thanks for testing. Too bad, I thought this could have ben the source of the problem 
Re-reading this thread again, I explicitly added the following users settings block in my dtable_web_settings.py because I thought the definition of the default role permissions could be a problem, but it didn’t change anything.
ENABLED_ROLE_PERMISSIONS = {
'default': {
'can_add_dtable': True,
'can_add_group': True,
'can_generate_external_link': True,
'can_create_common_dataset': True,
'can_run_python_script': True,
'can_use_advanced_permissions': True,
'can_use_advanced_customization': True,
'can_use_external_app': True,
'can_use_automation_rules': True,
'can_archive_rows': True,
'role_asset_quota': '',
'row_limit': -1,
'big_data_row_limit': -1,
'big_data_storage_quota': '',
'scripts_running_limit': -1,
'snapshot_days': 180,
'share_limit': 100
},
'guest': {
'can_add_dtable': False,
'can_add_group': False,
'can_generate_external_link': False,
'can_create_common_dataset': False,
'can_run_python_script': False,
'can_use_advanced_permissions': False,
'can_use_advanced_customization': False,
'can_use_external_app': False,
'can_use_automation_rules': False,
'can_archive_rows': False,
'role_asset_quota': '',
'row_limit': -1,
'snapshot_days': 30,
'share_limit': 100
},
}
If you can advise me in which direction to look to solve the problem, I’d greatly appreciate it.
Bests,
Benjamin
