How do you currently handle this with other services? I don't recall seeing a way to CC an arbitrary address in other SAAS products, but maybe I just haven't looked carefully enough.

As a workaround, you could perhaps register an account like mycompany-billing-department on phacility.com, set the address to receipts@mycompany.com, and then add them to the billing account (Instances → Your Instance → Manage Payment Account → Edit Account). You won't be billed for this account if you don't actually invite it to your instance.

Note that this will give the account total control over the instance, see "Allowing Other Users to Make Changes" here:

https://admin.phacility.com/book/phacility/article/managing/

(If "finance department" is approximately "a single human with an existing account", you can just add them to the payment account to achieve the same effect -- but they'll have total control over the instance.)

@epriestley I think they esentially want this: https://help.github.com/articles/setting-your-organization-s-billing-email/

Yes - it would be great to have a "billing contact" email for these kinds of things.

T7607 might help here as well.

From elsewhere, it would also be nice if this tokenizer highlighted instance members of instances associated with the billing account. There isn't a straightforward way to determine which "joe" or whatever is correct right now that works better than "ask Joe what his account name is".

Implementing this without hard-coding a bunch of Phacility-specific stuff into the upstream is tricky, though.

From elsewhere, it would also be nice if this tokenizer highlighted instance members of instances associated with the billing account. There isn't a straightforward way to determine which "joe" or whatever is correct right now that works better than "ask Joe what his account name is".

@chad -- I think this is a possible use case for the in-tokenizer dropdown from the other day. It wouldn't be completely clean but defaulting this tokenizer to "members of the instance" would probably be a better (specifically: safer) behavior than "all users".

This is kind of messy becuase it should really default to "Members of Instances Connected to this Payment Account", which isn't intuitive or concise and isn't an ApplicationSearch filter that's even possible to build. So the datasource itself would have to be custom.

This feels marginal to me overall, but maybe we'll turn up another half-dozen marginal cases and start to have a reasonably good motivation for building the dropdown filter.