I'm trying to create a Managed Package that relies entirely on Permission Sets. No profiles!

In my head, Profiles are really "owned" by each org administrator. One needs *serious* justification to hijack the one-and-only bite at the cherry and expect package installors to reassign user profiles. The great thing about Permission Sets is they are "owned" by the vendor and allow the admin to enrich and decorate accordingly. But that's enough about my perception of good platform citizenship :-)

Here's what the Permission Set looks like in the packaging / release org:

![package](https://i.stack.imgur.com/EawGm.png)

But here's how it looks installed into another organization: (**no assignments, no edit button!!!**)

![install](https://i.stack.imgur.com/2m1Jt.png)

Here's what I can fathom so far:

* this is similar to the [widely](https://salesforce.stackexchange.com/q/1325/320) [reported](https://salesforce.stackexchange.com/q/23194/320) loss of Custom App visibility
* the [Metadata API cannot assign record types](https://salesforce.stackexchange.com/a/13766/320) so one can't automate a post-install mechanism
* nobody is going to use a packaged custom profile just for my shitty little app

So in the interests of best practise: **how, today, should we package Record Type Assignments**?