Multisig account issues

[ty-zyp]

1、When using the createMultiSig account to create a multi-signature account, can only add accounts without identity? Although an account with an identity can be successfully added, an error is reported when the other party calls the accept method.（"Error: The target Account is already part of an Identity"） 2、After adding an unidentified account as a multi-signature account, log in with the multi-signature account, and any operation involving permissions will report an error（"TypeError: Cannot read properties of undefined (reading 'permissions')"） 3、If a multi-signature account is added to an account without identity, do I need to add permissions to this multi-signature account? How do I add permissions?

[lixianbin1]

• None of the signing Accounts can be associated with an Identity when accepting the Authorization
• I think there's a problem here
• It will be available to all the places where the account is used to make selections and need to be funded before use.

[F-OBrien]

@ty-zyp

1. This is by design. Signing accounts must be unassigned and do not hold funds. Signing identities are independent identities. The multisig itself must be attached to an identity to transact.
2. I'm not clear as to what you mean by logging in in the context of the SDK? As per 1 Multisig signing keys are not attached to an identity and hence are not individually permissioned.
3. When you create the authorization to join the multisig to the identity you specify the permissions for that multisig. see inviteAccountParams https://github.com/PolymeshAssociation/polymesh-sdk/wiki/api.procedures.types.InviteAccountParams. You can also edit permissions for a multisig in the same way you edit permissions for an secondary key.