aebrown wrote:it's hard to imagine why you wouldn't just use that standard calling.
Welcome to the forum! aebrown is correct, but I can see a couple of reasons why you might want a custom calling.[INDENT] 1) You are using the custom calling to describe his duties-[/INDENT][INDENT][INDENT]
Ward Assistant Clerk - some task (listing whatever he has an assignment to do) or,
[/INDENT][/INDENT][INDENT]2) You have two Ward Assistant Clerks for membership and/or for finance and are trying to designated one as subordinate to the other. You may have:[INDENT]
Ward Assistant Clerk-Membership, and you also want to call a
Ward Assistant Clerk-Membership- some task (listing of whatever task he assists the Membership clerk with, or that he is the "junior" membership clerk, or whatever.)
[/INDENT][/INDENT]Many of these are traditions of your ward or stake. The access table
here (lds.org clerk resources) shows differences in rights between between the Clerk and an Assistant Clerk. If it's the first example above, doing two callings is the only way to preserve your custom calling and grant the rights of the standard calling.
If it's the second, a ward assistant clerk-membership shows no more rights than a ward assistant clerk, so if it is the second example above, keep one as Membership, and add the second as one (or maybe one of several) Ward Assistant clerk(s), and tell him his duties.
You'll need at least clerk access to see the access table...
(afterthought: Unlike a ward clerk, where I believe you can only call one, you can have multiple membership or finance assistant clerks, just not in any hierarchical order)