Anonymous
My feedback
19 results found
-
2 votes
Anonymous
shared this idea
·
-
8 votes
Anonymous
supported this idea
·
-
166 votes
An error occurred while saving the comment -
3 votes
Anonymous
shared this idea
·
-
300 votes
Anonymous
supported this idea
·
-
1,043 votes
Anonymous
supported this idea
·
-
358 votes
Anonymous
supported this idea
·
-
1,517 votes
Anonymous
supported this idea
·
-
242 votes
Anonymous
supported this idea
·
-
3,048 votes
Anonymous
supported this idea
·
-
143 votes
Anonymous
supported this idea
·
-
65 votes
Anonymous
supported this idea
·
-
25 votes
An error occurred while saving the comment
Anonymous
commented
Alternatively, we could get a drop-down/list of existing aliases to select from, when editing a filter with the "receiver" option selected.
At least it eases the flow, and works for existing filters as well.
Anonymous
supported this idea
·
-
111 votes
Anonymous
supported this idea
·
-
117 votes
Anonymous
supported this idea
·
-
490 votes
Anonymous
supported this idea
·
-
310 votes
Anonymous
supported this idea
·
-
401 votes
Anonymous
supported this idea
·
-
582 votes
Anonymous
supported this idea
·
Only using the root domain is actually an issue as well. E.g. I have two completely different sites I need to log in to, but they both share .zendesk.com as the root domain.
Ideally We would be able to toggle on the pass record if it should use the complete URL for login filtering, or if it can rely solely on the root domain.