-
Notifications
You must be signed in to change notification settings - Fork 762
[DBR-2559] HTTP Bridge Documentation #9546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DBR-2559] HTTP Bridge Documentation #9546
Conversation
8d39baf to
515762c
Compare
MarkvanMents
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@atmosfer
Thanks for the PR - I've restructured it a bit. Can you check it looks OK?
Thanks.
| #### Users for Event Broker Manager | ||
|
|
||
| Users within the company's email domain that have a Mendix login can participate in the administration of the Mendix Event Broker as either a View or Admin user. They can also be blocked from participation. | ||
| Users within the company's email domain that have a Mendix login can participate in the administration of the Mendix Event Broker as either a View or Admin user. They can also be blocked from participation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still email domain limited - I understand that we are moving to tenants which can have more than one email domain?
| {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_internal_user_2.png" >}} | ||
|
|
||
| Users that are not part of the customer organization (not within the email domain of the customer) can be invited within the same levels of access. Such users still require a standard Mendix login. | ||
| Users that are not part of the customer organization (not within the email domain of the customer) can be invited with the same levels of access. Such users still require a standard Mendix login. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Email domain mentioned again - is it not better to talk about organizations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these user details should be obscured.
| {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_internal_user_2.png" >}} | ||
|
|
||
| Users that are not part of the customer organization (not within the email domain of the customer) can be invited within the same levels of access. Such users still require a standard Mendix login. | ||
| Users that are not part of the customer organization (not within the email domain of the customer) can be invited with the same levels of access. Such users still require a standard Mendix login. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't it be "Users who are ..."?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
It depends on whether you are talking about people or not.
If you are talking about people (users who do something) then it doesn't really make sense to say that the people are "within the email domain of the customer" as real people are not entities with email domains. So I would say that we are talking about an abstract entity (a Mendix user) not a real person and therefore I would use "users that are … not within the email domain of the customer".
|
Approved over Slack. |
Added HTTP Bridge Documentation