You can create an epic or a story in one circle (e.g. a customer circle) with the initial user story and then delegate the epic/story to another circle (e.g. a primary circle) for further refinement and implementation. The team in the customer circle will still be able to follow the state of the epic.
In the Circle Map the links between circles define, to which circles the epics/stories can be delegated.
The epic/story seen from both circles
The state, title, user story and description will always be the same seen from both circles. If e.g the user story is modified by the team in one of the circles, the other team sees the changes as well.
Users from both circles can enter epic comments, and the comments can be read and replied to by both teams.
The delegated epic can, however, be assigned to different releases in the two circles. It can have different assignment to user/team and it can have different value and effort estimates.
Activity logging for when delegating, cancelling delegation and changes is also done across both circles for the delegated entities.
What you can do with the epic/story in the customer circle
The team in the customer circle will usually enter the user story text before the epic/story is delegated to a primary circle. They may also place the epic/story in a release to indicate the expected deadline. And they could enter value estimates for the epic/story.
When the epic/story has been delegated, the team in the customer circle can still follow the state of the epic/story. A user with manager rights is able to change the user story and description, but will usually not do this, as they have handed over the epic/story to the primary circle team.
If the epic had child stories or epics, these are moved to the circle delegated to. They are not visible anymore in the customer circle, and it is not possible to create new stories or epics below the delegated epic.
The epic/story can be planned to a release if needed but not to a sprint. This limitation is based on the theory that any delegated work will be tactically implemented in the destination circle.
Attachments can be added to, edited and also deleted from the epic/story and this will be reflected in the primary circle.
What you can do with the epic/story in the primary circle
When the epic/story has been delegated to the primary circle, this is where it is handled from now on.
Any stories or epics below the delegated epic are moved to this circle. The team can add more child stories and place these in sprints for implementation.
Attachments can be added to, edited and also deleted from the epic/story and this will be reflected in the customer circle.