Björn Pedersen
Björn Pedersen
make sure you have the following in your grafana.ini: ``` feature_toggles: accessControlOnCall: false enable: ...,externalServiceAccounts,... (any other features you may want) ``` and *restarted* your grafana instance.
Do you happen to have more than one organization in your grafana instance? Then see https://github.com/grafana/oncall/issues/5100#issuecomment-2386949587
see also #5100
One of the things to keep in mind here is: The production frontend is served from compiled sources (nginx serving static files, no node available inside the conatiner), but for...
grafana 11.3.0 has been disabled in the e2e test currently (#5207 ) so I guess oncall is currently not compatible. Looking at the changes in grafana 11.3.0, https://github.com/grafana/grafana/pull/93849 seem like...
I like the idea. An alternative to strict binding could be, that registrations with non-matching emails ( if an indico account exists, we probably want to match against all emails...
 I'll try to create a demo in the sandbox as well.
https://sandbox.getindico.io/event/4739
I see your point. Possibly a breakpoint before the title with higher priority would help here.